[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug reporting proceedure, was Re: Bug#24066: libc6: rsh segfaults as , a result of new libc 2.0.7r2



On Wed, Jul 15, 1998 at 09:49:33PM -0500, John Goerzen wrote:
> Dale Scheetz <dwarf@polaris.net> writes:
> 
> > > NO!  Let's not annoy bug submitters!
> > 
> > But annoying developers is just fine ;-)
> 
> Yes.  Because the usual reason for something to not be closed is that
> the developer either forgot to close it or hasn't done anything about
> it yet.

I agree with John here. Dale, for small to medium packages, duplicated
bug reports are not a problem at all (indeed I´m happy if something
is brave enough to report a bug). If I know about bugs in my packages which
never are reported -- is nobodyone using my package or what?

However, there are some packages were the number of bugs reported and
open is terrible, and it requires a lot of work to clean this up.

I was surprised about your complaint. The last time, you just asked
for some people to help you with the bug reports. I remember that
I thought this was the right reaction. Has this changed? Some people
have offered you their help. Why didn´t you asked again?

FWIW, i you need help with the bug reports, I can take a look at
them. Just let me know.

Marcus


-- 
"Rhubarb is no Egyptian god."        Debian GNU/Linux        finger brinkmd@ 
Marcus Brinkmann                   http://www.debian.org    master.debian.org
Marcus.Brinkmann@ruhr-uni-bochum.de                        for public  PGP Key
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/       PGP Key ID 36E7CD09


--  
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: