Re: freebsd-bugbusters Digest, Vol 245, Issue 1
Daniel Tedman <[email protected]> Tue, 25 Dec 2012 20:28:14 +1000
| Newsgroups | gmane.os.freebsd.bugbusters |
|---|---|
| Message-ID | <[email protected]> |
On 22/12/2012, at 10:00 PM, [email protected] wrote: > Send freebsd-bugbusters mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-bugbusters > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-bugbusters digest..." > > > Today's Topics: > > 1. closing fixed PRs (Mark Johnston) > 2. Re: closing fixed PRs (Eitan Adler) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 21 Dec 2012 16:07:55 -0500 > From: Mark Johnston <[email protected]> > To: [email protected] > Subject: closing fixed PRs > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > Hello, > > There are a few PRs (166994 and 169642 for example) where the reported > issue has been independantly fixed and the submitter doesn't seem to be > interested in a patch for their tree. What's the right way to handle > them? I don't see any reason for them to stay open. I was thinking of > setting them to feedback mode and waiting a week before closing them. Is > this alright? > > Thanks! > -Mark > > > ------------------------------ > > Message: 2 > Date: Fri, 21 Dec 2012 16:26:28 -0500 > From: Eitan Adler <[email protected]> > To: Mark Johnston <[email protected]> > Cc: [email protected] > Subject: Re: closing fixed PRs > Message-ID: > <CAF6rxgn6MJYr9mvFrqYApzXYyLAo6djE7AACntujEUj37+OAhQ@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On 21 December 2012 16:07, Mark Johnston <[email protected]> wrote: >> Hello, >> >> There are a few PRs (166994 and 169642 for example) where the reported >> issue has been independantly fixed and the submitter doesn't seem to be >> interested in a patch for their tree. What's the right way to handle >> them? I don't see any reason for them to stay open. I was thinking of >> setting them to feedback mode and waiting a week before closing them. Is >> this alright? > > If you are sure the reported issue has been fixed please set them to > patched - if it has not yet been MFCed > closed - if it has been MFCed or never will be > > in the message please mention the relevant commit numbers > > please assign them to the committer who fixed it. > > example: > > change-pr -p -T markj -m "fixed in r12345 - will be MFCed shortly" docs/78965 > > > -- > Eitan Adler > > > ------------------------------ > > _______________________________________________ > [email protected] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-bugbusters > To unsubscribe, send any mail to "[email protected]" > > > End of freebsd-bugbusters Digest, Vol 245, Issue 1 > ************************************************** _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugbusters To unsubscribe, send any mail to "[email protected]"