Date: Mon, 03 Dec 2018 02:51:43 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 232326] sysutils/mkdesktop: Update to 2.0 Message-ID: <bug-232326-7788-S6vasAGDDw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-232326-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-232326-7788@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=3D232326 --- Comment #33 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to bourne.identity@hotmail.com from comment #32) Bugzilla has flags, which when set to ? <email> send notifications to said <email> requesting action. Generally speaking, setting flags means something has been requested, detai= ls of which are usually in a comment. Examples of things that are requested, updated patches, general feedback/answer to a question, request for QA/test= ing, request for logs/error details/system information. In this case/issue, the maintainer-feedback flag has been set (?), with your email as the requestee. You can hover over the flag name for a more detailed description of its use, and possible actions. At some point in the past (just after comment 13, an updated patch and QA/testing was requested.=20 If those issues have been taken care of, just set the maintainer-feedback f= lag to "+", which means acknowleged/done, but I can see that there's some outstanding questions or issues (eg: comment 30), so its best to address th= ose before acknowledging the flag. While we're here I would also set the shar attachment as obsolete (effectiv= ely hiding it). Port updates are to be provided in unified/svn diff format, and having two attachments that do the same thing can be confusing, delaying progress/review --=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-232326-7788-S6vasAGDDw>