From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Joe Buck <jbuck@synopsys.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: patch tracking
Date: Fri, 14 Sep 2001 14:24:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.33.0109142313060.55386-100000@deneb.dbai.tuwien.ac.at> (raw)
In-Reply-To: <200109141902.MAA15299@atrus.synopsys.com>
On Fri, 14 Sep 2001, Joe Buck wrote:
> First, we want to decrease the number of patches that the overworked
> experts must handle, by having a pre-screening process.
Also, we should abondon the "Bootstrap running, okay if it passes? --
Please forget the previous patch, here is a new one!" scenario we have
been seeing increasingly often.
> I realize that GNATS is not ideal for patch-tracking, but it's already
> in place.
Some projects like FreeBSD are using GNATS for tracking patches; it's
not perfect, but it works relatively well AFAIK.
Gerald
(In the past I twice suggested to use GNATS to avoid patches falling
through the cracks, but in both cases there wasn't a single reply. OTOH,
my proposal was by far less elaborate than the current one. ;) )
next prev parent reply other threads:[~2001-09-14 14: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
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 [this message]
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=Pine.BSF.4.33.0109142313060.55386-100000@deneb.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.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).