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 [thread overview]
Message-ID: <200109142152.OAA18710@atrus.synopsys.com> (raw)
In-Reply-To: <20010914140254.F443@codesourcery.com>
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
next prev parent reply other threads:[~2001-09-14 14:53 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
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 [this message]
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=200109142152.OAA18710@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=zack@codesourcery.com \
/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).