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

Re: Unanswered problem reports

> From: Michael E. Deisher <deisher@enws428.EAS.ASU.EDU>
> Subject: Re: Unanswered problem reports

> On Fri, 18 Aug 1995 11:29:50 -0400, rdm@tad.micro.umn.edu said:
> > There's two things I'd like to see:
> > (1) A way of assigning a bug report to some specific package, if the
> > Package: field is blank.
> It's easy.  You just reject the faulty bug report and tell the person
> who sent it to resubmit it properly.  :-)  I think this is already
> done.

Sometimes, it is not possible to tell just were a problem lies.  What do
we do with the Package: field in this case?

> > (2) A way of sending to the most recent package maintainer of each
> > package with bugs a bug report summary specific to that package.
> That's ok as long as the package maintainer has an e-mail address.
> A friendly reminder to those who do might be effective.

Please, whoever does this, make it one message.  I only have two oustanding
bug reports (one of which need to be marked as done), but some of us (I'm
thinking of Ian M. or prehaps Bruce) are maintaining so many packages, that
they would get buried alive under the flood of e-mail if each bug were to
generate a seperate message.

   David H. Silber     dhs@firefly.com     Project:  Debian GNU/Linux (uucp)
   <http://www.access.digex.net/~dhs/>     Wanted:  Spare time.

Reply to: