Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e")
On Mon, 02 Jun 2003 22:29:56 +1000, Herbert Xu <firstname.lastname@example.org> said:
> Josip Rodin <email@example.com> 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
>>> firstname.lastname@example.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 package.
> 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?
Cause I need to go trolling for external references at a time
I may not be able to to see what the bug was, and how it was
fixed. What is so onerous about stating :
* upstream version x.y.z changed locking for struct A that fixes the
crash when doing Y; closes: Bug#12345
* upstream version x.y.z changed documentation to match the actual
behaviour when user does Y closes: Bug#12347
* upstream version x.y.z now includes feature Z closes: Bug#12349
Anyone so extrmely lazy as to find writing changelog entries
like above is likely too lazy to be doing a good job as a maintainer.
Joshu: What is the true Way? Nansen: Every way is the true Way. J: Can
I study it? N: The more you study, the further from the Way. J: If I
don't study it, how can I know it? N: The Way does not belong to
things seen: nor to things unseen. It does not belong to things known:
nor to things unknown. Do not seek it, study it, or name it. To find
yourself on it, open yourself as wide as the sky.
Manoj Srivastava <email@example.com> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C