Date: Fri, 09 Feb 1996 10:30:29 -0800 From: Paul Traina <pst@shockwave.com> To: Poul-Henning Kamp <phk@critter.tfs.com> Cc: committers@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: What's up with bug assignments? (please read) Message-ID: <199602091830.KAA19249@precipice.shockwave.com> In-Reply-To: Your message of "Fri, 09 Feb 1996 10:41:18 %2B0100." <4353.823858878@critter.tfs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> To: Paul Traina <pst@shockwave.com> > cc: committers@freebsd.org, freebsd-bugs@freebsd.org > Subject: Re: What's up with bug assignments? (please read) > Date: Fri, 09 Feb 1996 10:41:18 +0100 > From: Poul-Henning Kamp <phk@critter.tfs.com> > > > http://www.freebsd.org/cgi-bin/query-pr-summary.cgi?engineer=summary > > One more, how do I get the unassiged ones ? engineer=none ? I'll add a special thing for unassigned bugs once the backlog comes down. For now, feel free to take bugs away from other people if you feel they're in your area or you know how to fix them (send them e-mail to be polite). I've been assigning bugs in large batches, and in a number of cases, I did not pick the optimal person. Just look at the general summary. We could use another state, that indicates that a bug is being actively worked on. If you see a bug assigned to someone else and you think you know what's up with it, just go for it. Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602091830.KAA19249>