public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: egcs@thewrittenword.com
To: gcc@gcc.gnu.org
Subject: Re: patch tracking
Date: Fri, 14 Sep 2001 12:24:00 -0000	[thread overview]
Message-ID: <20010914142350.A99005@oolong.il.thewrittenword.com> (raw)
In-Reply-To: <200109141902.MAA15299@atrus.synopsys.com>

On Fri, Sep 14, 2001 at 12:02:07PM -0700, Joe Buck wrote:
> The biggest problem facing GCC seems to be that patches aren't getting
> reviewed.  I think it's a process problem; we don't have a system for
> keeping track of patches, and the load on the people qualified to
> approve patches is too high.  As a result, it's very difficult for
> people without blanket write privs to effectively contribute to the
> project; the turnaround for patch review can be months.  This means
> we're not getting the problems fixed and the frustration level is high.

savannah.gnu.org is running sourceforge which contains a patch
manager. Maybe this could be an option.

-- 
albert chin (china@thewrittenword.com)

  parent reply	other threads:[~2001-09-14 12:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-14 12:02 Joe Buck
2001-09-14 12:21 ` Diego Novillo
2001-09-14 12:24 ` egcs [this message]
2001-09-14 12:28 ` Joseph S. Myers
2001-09-14 12:35   ` Phil Edwards
2001-09-14 14:03 ` Zack Weinberg
2001-09-14 14:16   ` Phil Edwards
2001-09-14 14:51     ` Joe Buck
2001-09-14 15:53     ` Zack Weinberg
2001-09-14 14:53   ` Joe Buck
2001-09-14 15:48     ` Zack Weinberg
2001-09-14 14:24 ` Gerald Pfeifer
2001-09-15  3:07 ` Bernd Schmidt
2001-09-16 14:46   ` Joe Buck
2001-09-18 16:18     ` Marc Espie
2001-09-18  9:49 dewar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010914142350.A99005@oolong.il.thewrittenword.com \
    --to=egcs@thewrittenword.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).