On Sun, Jun 01, 2003 at 11:16:36AM +0200, Marco Presi wrote: > || On Mon, 19 May 2003 14:01:29 -0700 > || Brian Nelson <[EMAIL PROTECTED]> wrote: > >> Changes: > >> pointless (0.3-3) unstable; urgency=low > >> . > >> * Closes: #193287 > >> * Closes: #193286 > > bn> Uhhh, nope, sorry. Close them correctly or don't close them at all. > > ??? > > Are you sure? It works well here... > > Could you send me more information?
Sure, it "works" in that it closes the bugs, but it conveys very little useful information to the submitter, people watching lists like debian-bugs-closed, people reading apt-listchanges output, or people reading through the changelogs next year looking for when a problem was fixed. Instead of just "* Closes: #nnnnn", please say "* Fixed incorrect frobbing of foo, closes: #nnnnn" - i.e. give a description of what was changed. (Now that the bugs have been reopened, in this particular case just mail [EMAIL PROTECTED] with a description of what was changed. Brian's rightly trying to suggest that your changelogs should include some detail of the changes in the future, though.) Thanks, -- Colin Watson [EMAIL PROTECTED]