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

Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e")

Josip Rodin <joy@srce.hr> wrote:
> On Mon, Jun 02, 2003 at 09:07:00PM +1000, Herbert Xu wrote:
>> what if the maintainer uploads a new upstream release which happens to fix
>> bug #xxx, and then sends a message by hand to xxx-done@bugs.debian.org
>> with the message "This bug is fixed in upstream version x.y.z".
> The submitter would still have little information on what happened.
> It's not like anything bad would happen to the maintainer if they say
> a bit less tersely what closed the bug.

Let me make this a bit more concrete.  Let's say that a user files a
bug report saying that the kernel crashes when he does X, or that
doing Y does not work as documented, or feature Z is missing from the

What exactly is wrong with a message sent to the BTS by hand saying the
"this is fixed in upstream version x.y.z"? Do we really expect our
developpers to hunt down the technical details of each upstream bug
fix before closing them? Does the user really care?

I bet that most users simply don't give a damn.  For the few that are
interested in the internals of the package in question, they can either
read the diff themselves, or even send a question to the developper.
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Reply to: