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: Craig Rodrigues <rodrigc at attbi dot com>
- To: Wolfgang Bangerth <bangerth at ticam dot utexas dot edu>
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 8 Mar 2003 10:04:05 -0500
- Subject: Re: GCC review process: how to handle external submissions
- References: <Pine.LNX.4.44.0303080018030.7911-100000@gandalf.ticam.utexas.edu>
On Sat, Mar 08, 2003 at 12:40:09AM -0600, Wolfgang Bangerth wrote:
>
> This week, I got three mails on the same subject, two of which read like
> this:
>
> > I submitted this to gcc-patches in November, resubmitted it in December,
> > opened a bug report in January, wrote to gcc-bugs. I got no replies.
This has been a problem for quite a while.
I have the following recommendations once Bugzilla is fully set up:
- eliminate the gcc-gnats mailing list (keep around the archives)
- send all new entries and followups entered in Bugzilla to gcc-bugs
I notice that people enter reports and sometimes patches in GNATS,
but few people read gcc-gnats.
There are too many mailing lists to follow, i.e. gcc-gnats, gcc-patches,
gcc-bugs, so sometimes patches submitted by end-users fall through
the cracks.
My recommendation won't solve all the problems, but it is an
idea to consolidate some lists to make things easier to follow.
--
Craig Rodrigues
http://home.attbi.com/~rodrigc
rodrigc at attbi dot com