On Mon, May 26, 2003 at 11:13:24PM -0700, Brian Nelson wrote:
Why do so many seem to have difficulty with this concept?
They're lazy.
Is it worthwhile to Cc this stuff to -devel,
Yes. It calls out the offenders for public shaming. If they honestly
didn't know about the recommended best
On Tue, May 27, 2003 at 07:41:34PM -0700, Brian Nelson wrote:
Steve Langasek [EMAIL PROTECTED] writes:
you're getting upset about bug closings that absolutely *do* include a
description of what the maintainer changed in order to fix them:
incorporating a new upstream release. That this is
Hi, Brian Nelson wrote:
Is it
worthwhile to Cc this stuff to -devel, or should I just give up and let
the proliferation of these IMO useless changelogs continue? (serious, not
rhetorical, questions)
IMHO you should continue. Peer pressure is a powerful concept. ;-)
--
Matthias Urlichs |
reopen 159971
reopen 124472
reopen 147059
reopen 70184
thanks
Anselm Lingnau [EMAIL PROTECTED] writes:
Format: 1.7
Date: Tue, 27 May 2003 01:15:33 +0200
Source: bwidget
Binary: bwidget
Architecture: source all
Version: 1.6.0-1
Distribution: unstable
Urgency: low
Maintainer: Anselm
On Mon 26 May 2003, Brian Nelson wrote:
Umm, no, the changelog is for listing changes (*change* log, get it?),
not for just closing bugs without any reason given whatsoever.
Why do so many seem to have difficulty with this concept? Is it
worthwhile to Cc this stuff to -devel, or should I
Paul Slootman [EMAIL PROTECTED] writes:
On Mon 26 May 2003, Brian Nelson wrote:
Umm, no, the changelog is for listing changes (*change* log, get it?),
not for just closing bugs without any reason given whatsoever.
Why do so many seem to have difficulty with this concept? Is it
worthwhile
On Tue, May 27, 2003 at 08:39:50AM -0700, Brian Nelson wrote:
Perhaps a separate, concise message to debian-devel-announce?
I doubt it would help. I see changelog abuse as an act of laziness, not
ignorance. Common sense says that you should be listing changes in the
changelog. It's not
Josip Rodin [EMAIL PROTECTED] writes:
On Tue, May 27, 2003 at 08:39:50AM -0700, Brian Nelson wrote:
Perhaps a separate, concise message to debian-devel-announce?
I doubt it would help. I see changelog abuse as an act of laziness, not
ignorance. Common sense says that you should be
Christian Kurz [EMAIL PROTECTED] writes:
Hi Brian
On [26/05/03 23:13], Brian Nelson wrote:
Anselm Lingnau [EMAIL PROTECTED] writes:
[...]
* Closes: #159971, #124472, #147059, #70184.
Umm, no, the changelog is for listing changes (*change* log, get it?),
not for just closing bugs
On Tue, May 27, 2003 at 12:15:37PM -0700, Brian Nelson wrote:
1. To show others, especially NM's, what not to do. NM's mostly learn
by example, and I think it helps to ensure they don't follow bad
examples.
2. It's something that should be obvious. Producing poor quality
Steve Langasek [EMAIL PROTECTED] writes:
On Tue, May 27, 2003 at 12:15:37PM -0700, Brian Nelson wrote:
1. To show others, especially NM's, what not to do. NM's mostly learn
by example, and I think it helps to ensure they don't follow bad
examples.
2. It's something that should be
On Tue, May 27, 2003 at 07:41:34PM -0700, Brian Nelson wrote:
Obvious is a key word indicating that you need to check your
assumptions at the door. While I will certainly concede that changelogs
that spell out the nature of relevant upstream changes are more useful
than those which do
12 matches
Mail list logo
