I agree with the sentiment which I think Bastian Blank is expressing. It is a documented best-practice to document what change caused each bug to be closed.
http://www.us.debian.org/doc/manuals/developers-reference/ch-pkgs.en.html#s-upload-bugfix The idea is that bug reporters will get ample information in the 'close' message, rather than just a note that 'a bug you reported was fixed'. If the bugs were all fixed because of the "new upstream release", I would have expected the close entries to be indented below the comment for that release. Furthermore, since you are the upstream author, it should be simple to provide more information. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
