Date: Thu, 30 Jun 2016 06:57:08 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 209742] devel/godot: Improve port (v2.0.3) Message-ID: <bug-209742-13-LVa0N8f0Hi@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209742-13@https.bugs.freebsd.org/bugzilla/> References: <bug-209742-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209742 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open --- Comment #35 from Kubilay Kocak <koobs@FreeBSD.org> --- I thought I'd drop in to say great job to you both on collaborating on this issue and using the tracker features very well. Keep it up! :) Tips: The issue summary should always reflect the overall changes, particularly if that changes over time. The issue currently only mentions one port, and not what the overall changes are. Something like: "[NEW PORT] devel/godot-tools: ${COMMENT}, Improve devel/godot" In most cases, its preferred and recommended to separate new port additions from updates. The next best thing is separate attachments, which has been d= one here. Descriptions should include category/port so its clear what is for what (attachment 171968). A good rule of thumb to use is imagine its a commit message shortlog Poudriere logs are no longer required to be included as attachments. Instea= d, just write the following in your description/comments after confirming they PASS: - portlint: OK (looks fine.) - testport: OK (poudriere: <archs>, <versions> tested) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209742-13-LVa0N8f0Hi>