From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joe Buck <jbuck@synopsys.COM>
To: zack@codesourcery.com (Zack Weinberg)
Cc: jbuck@synopsys.com (Joe Buck), gcc@gcc.gnu.org
Subject: Re: patch tracking
Date: Fri, 14 Sep 2001 14:53:00 -0000
Message-id: <200109142152.OAA18710@atrus.synopsys.com>
References: <20010914140254.F443@codesourcery.com>
X-SW-Source: 2001-09/msg00576.html

Zack writes:

> I have been considering a very simple patch tracker which would work
> by monitoring the gcc-patches and gcc-cvs mailing lists.  The
> principle would be: every time a patch is posted to gcc-patches, it
> records the subject line and change log...

The problem is that there are too many things on gcc-patches that are
not patches but rather are discussion of patches, or are completely
untested hacks that don't deserve tracking.  That's why I want the
first-level filter.  We would try to set a deadline of no more than
N days before any new message that is a patch is either bounced or
goes into the system to be tracked.

> The program needs a way to get the URL of an archived message to
> gcc-patches.

Maybe the way to combine the ideas is that when the pre-screeners
approve a patch for further processing, they insert the URL into
your patch-tracker program.

Joe