On Sun, Nov 27, 2005 at 07:32:35PM +0000, Julian Gilbey wrote: > On Sun, Nov 27, 2005 at 12:10:48PM +0100, A Mennucc wrote: > > On Sat, Nov 26, 2005 at 07:09:06PM +0000, Julian Gilbey wrote: > > > On Sat, Nov 26, 2005 at 10:58:01AM +0100, A Mennucc wrote: > > > > add > > > > $ bts fixed #bugnumber #version > > > > as an alias to > > > > $ bts close #bugnumber #version > > > > indeed the purpose of that command is to set the "fixed" field in the > > bug report. > > Except that this command is deprecated, so I don't really want to add > an alias to it.
AFAIR the command is deprecated since the DD often would not explain why s/he closes the bug. So here is a good alternative: add a command $ bts fixed #bugnumber #version [why] that sends an email to nnnn-done with a Version: pseudo-header ; if [why] is specified, then that is the content of the email, otherwise if $ bts fixed #bugnumber #version is called then 'bts' asks for a body of the email message. > Use nnnn-done with a Version: pseudo-header instead. yes, but that is cumbersome and not so easy to spot in documentation: for example http://www.debian.org/Bugs/Developer mentions the pseudo-header but is not very clear a 'bts fixed' subcommand would be much easier > > Suppose moreover that somebody sends a > > > > $ bts close #wrongbugnumber #version > > > > where #wrongbugnumber is a mistyping: then it > > would be useful to have a command > > > > $ bts unfixed #wrongbugnumber #version > > > > to correct the former. > > Good question: I've submitted a bug against bugs.d.o as there does not > appear to be a canonically correct way to fix an error such as this. :-) so it is it! I was looking for that once (I *did* send a wrong 'close' email once ) and wondering if I had failed to understand the new BTS interface.. a. -- Andrea Mennucc "Ukn ow,Ifina llyfixe dmysp acebar.ohwh atthef" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
