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
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Cc: Craig Rodrigues <rodrigc at attbi dot com>,Wolfgang Bangerth <bangerth at ticam dot utexas dot edu>, <gcc at gcc dot gnu dot org>
- Date: Tue, 11 Mar 2003 18:29:02 -0500
- Subject: Re: GCC review process: how to handle external submissions
On Saturday, March 8, 2003, at 02:00 PM, Joseph S. Myers wrote:
On Sat, 8 Mar 2003, Craig Rodrigues wrote:
- eliminate the gcc-gnats mailing list (keep around the archives)
gcc-gnats is not a mailing list, it is the address on which GNATS
receives
and files new bug reports, follow-ups and spam. With Bugzilla it will
have a converter to receive gccbug format input and PR follow-ups and
file
them in Bugzilla (but not, I hope, continue to file spam as "pending"
bug
reports).
They won't be valid GNATS input, so it won't file them.
I've tried.
:)
gcc-prs is the mailing list that ought to be eliminated.
- send all new entries and followups entered in Bugzilla to gcc-bugs
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).
I'm a little unclear on what exactly you guys want (IE by "Bugzilla
address" do you mean seperate addresses for each bug or what) , but if
you hash it out and let me know, i should be able to make it happen.
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).
--
Joseph S. Myers
jsm28 at cam dot ac dot uk