This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC review process: how to handle external submissions
On Sat, Mar 08, 2003 at 07:00:36PM +0000, Joseph S. Myers wrote:
> gcc-gnats is not a mailing list, it is the address on which GNATS receives
OK. Maybe a gcc-bugzilla alias to gcc-gnats should be created
at some point (this is not critical) to preserve backwards compatibility,
but more accurately reflect what software is being used?
> Yes. Ideally (to avoid lots of duplication of messages on gcc-bugs), the
> messages should have the Bugzilla address for receiving follow-ups and
> filing them in their headers, but should not mention gcc-bugs in their
> headers (and gcc-bugs's spam protection should be set up to understand
> this). But duplication is better than the follow-ups being hidden (at
> present, if someone doesn't CC their follow-up to gcc-bugs, but only sends
> it to gcc-gnats, it only appears on gcc-prs, which few read).
I agree with you and I think I have seen Red Hat's Bugzilla setup
do what you ask.
They set the mail headers something like:
Return-Path: <bugzilla at redhat dot com>
From: bugzilla at redhat dot com
To: notting at redhat dot com, rodrigc at mediaone dot net
Subject: [Bug 6219] Changed - /etc/protocols is missing entries for IPv6
X-Mailer: Perl SMTP Module
X-Loop: bugzilla at redhat dot com
X-Keywords:
If you reply to that message, it will go to bugzilla at redhat dot com dot
So if something code be set up so that replying to a message
from gcc-gnats at gcc dot gnu dot org (or gcc-bugzilla at gcc dot gnu dot org) will:
(1) Have the From and Return-Path headers contain
gcc-gnats at gcc dot gnu dot org (or gcc-bugzilla at gcc dot gnu dot org)
(2) Put the e-mails of all the addresses registered in the PR
in the To: field.
(3) Also send the e-mail to gcc-bugs at gcc dot gnu dot org (or gcc-bugzilla)
That way, if a user replies to such a message, it will be sent
archived in Bugzilla *and* sent to gcc-bugs.
I think that would be nice.
--
Craig Rodrigues
http://home.attbi.com/~rodrigc
rodrigc at attbi dot com