Subject: Re: GNATS needs tweaking (CVS commit: src/usr.bin/printf)
To: David Laight <firstname.lastname@example.org>
From: Greg A. Woods <email@example.com>
Date: 06/25/2003 16:05:10
[ On Wednesday, June 25, 2003 at 14:01:00 (+0100), David Laight wrote: ]
> Subject: Re: CVS commit: src/usr.bin/printf
> Gnats is broken, you need to explicitly copy netbsd-bugs when replying
> to gnats mail.
GNATS isn't really broken -- it's just slightly mis-configured.
It should be relatively easy to add <netbsd-bugs> to the list of
addresses where all notifications are sent from edit-pr, as well to
where all notification of new submissions received by e-mail are sent.
For changes filed with edit-pr GNATS sends notifications to the
addresses in any "X-GNATS-Notify:" mail header in the PR, as well as
the normal "Reply-To:" or "From:" mail header. It shouldn't be too hard
to arrange for all PRs to have an appropriate "X-GNATS-Notify:" header
added automatically to them. The mail from edit-pr is sent in a shell
script too, so hard-coding "CC: <firstname.lastname@example.org>" in the header
of the generated message would also be very easy to do, though of course
someone needs to keep track of such patches so that an upgrade won't
Replies arriving by e-mail are filed in the normal way and the addresses
for the responsible parties of the catetgory, as well as the contacts
for the submitter-ID, all get full copies of the submission. Adding
<netbsd-bugs> to the appropriate contact lists is all that's needed to
get them copied to the list.
Greg A. Woods
+1 416 218-0098; <email@example.com>; <firstname.lastname@example.org>
Planix, Inc. <email@example.com>; VE3TCP; Secrets of the Weird <firstname.lastname@example.org>