I often see submitters wrongly following-up to a bug and describing
symptoms that are superficially similar to the original, but (to me
as maintainer) obviously a separate bug.
I can ask them to open a separate bug, or I can forward the message
to submit@bugs and the use 'submitter' to make it their bug, but it
is somewhat prone to failure.
It would be very useful to have a command that would turn a message
on an existing bug into a new bug. Ideally, the submitter, title,
etc. would be taken from that message as if it had been sent to
submit@bugs. This would also send a notification to the follow-up
submitter that they have a new bug number. I assume that actually
moving messages would be problematic, so perhaps the message could
be copied and then hidden-by-default in the original bug report?
It would also be useful to be able to copy multiple messages when
doing this, in case there were replies to the erroneous follow-up.
But that's relatively unimportant.
Kernel: Linux 2.6.32-5-486
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com
Archive: firstname.lastname@example.org dent.org.uk">http://email@example.com dent.org.uk