From: Marc Espie <espie@quatramaran.ens.fr>
To: jbuck@synopsys.com
Cc: gcc@gcc.gnu.org
Subject: Re: patch tracking
Date: Tue, 18 Sep 2001 16:18:00 -0000 [thread overview]
Message-ID: <200109182316.f8ING2h16678@quatramaran.ens.fr> (raw)
In-Reply-To: <200109162145.OAA02357@atrus.synopsys.com>
In article < 200109162145.OAA02357@atrus.synopsys.com > you write:
>There is one particular category of patch that I am especially eager
>to speed up: patches that fix severe breakage (like "won't bootstrap")
>on minority platforms. If we can't find a way to do that, as time
>goes on gcc will work on fewer and fewer platforms. We may need to
Putting on my `opressed OpenBSD minority' hat...
I concur.
I don't count the number of times I had to become completely obnoxious
just to get a nagging minor problem (and often complete with patches)
reviewed and in the mainline/the stable tree.
Many thanks to the very few fellow developers who can find the time to
help me (rth specifically, as he's helped me more often than not)
next prev parent reply other threads:[~2001-09-18 16:18 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
2001-09-15 3:07 ` Bernd Schmidt
2001-09-16 14:46 ` Joe Buck
2001-09-18 16:18 ` Marc Espie [this message]
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=200109182316.f8ING2h16678@quatramaran.ens.fr \
--to=espie@quatramaran.ens.fr \
--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).