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: Steven Bosscher <s dot bosscher at student dot tudelft dot nl>
- To: Wolfgang Bangerth <bangerth at ticam dot utexas dot edu>
- Cc: Craig Rodrigues <rodrigc at attbi dot com>, gcc at gcc dot gnu dot org
- Date: 10 Mar 2003 16:14:02 +0100
- Subject: Re: GCC review process: how to handle external submissions
- References: <Pine.LNX.4.44.0303100841220.7911-100000@gandalf.ticam.utexas.edu>
Op ma 10-03-2003, om 15:45 schreef Wolfgang Bangerth:
>
> > > > 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.
> > [...]
> > 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.
>
> This is not the structural problem we should talk about. Note that this
> person sent a patch to *gcc-patches* three times without response. This
> applies to at least several of the patches in gnats as well. Heck, I have
> done that myself and got no response.
Does bugzilla provide an option to mark PRs that have a patch?
> The problem is not that these messages are not seen -- I bet they are, but
> nobody feels responsible. We need to have someone with a respected name
> (so that he can ask reviewers to look at something) who takes over this
> responsibility.
Maybe a patch database would help? This could be part of the bug
database, or something completely separate. gcc-patches is too much a
discussions list to serve as a patch database.
Greetz
Steven