On Mon, Dec 10, 2001 at 12:54:43PM +0000, Mark Brown wrote: > You can still close bugs by mailing nnnnn-done@bugs.debian.org. The > problem with using closes rather than this is that the submitter just > gets notified that their bug has been closed with no explanation as to > why. If you mail -done a copy of the mail gets sent to the submitter, > hopefully explaining why the bug has been closed. Yes, I know, but with the two examples i reported a DD do not need to explain the reason: in the first case, the change-log file should list the changes and their reason; in the second case, the existence of the package is the reason. Sending an email to the submitter would be glad, sure, but would introduce redundancy of information, and would be quite annoying. Please, do not reply with shell-scripts showing various way of closing bugs with mail command etc: first, because i know how to write one, second i cant use them to send a single mail to manipulate a list of bug with other bts commands. If the problem is that no explanation is sent with the close command, I think that this is only a matter of kindness of the DD manipulating the bugs; I prefer to teach people to behave in the better way for the community, rather than deny the whole community to do something. Cheers, -- Luca - De Whiskey's - De Vitis aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$
Attachment:
pgpaz66Zpd1kd.pgp
Description: PGP signature