From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Russ Allbery <rra@stanford.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: What is the relationship between GCC and Cygnus / Red Hat?
Date: Fri, 16 May 2003 08:53:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.55.0305161049180.9885@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <ylhe84yx35.fsf@windlord.stanford.edu>
On Fri, 9 May 2003, Russ Allbery wrote:
> I certainly have no objections to removing it entirely; GCC and in general
> GNU toolchain development hasn't looked even remotely dominated by Cygnus
> or Red Hat to me for a long, long time now. But if that isn't acceptable
> for whatever reason, an alternate suggestion:
Thanks for the alternate suggestion!
Taking into account the original feedback, and after waiting another week
for further feedback, I applied I my original patch:
http://gcc.gnu.org/ml/gcc/2003-05/msg00894.html
Joe's point that this is in fact not a FAQ certainly helped convince me
that this is indeed the right approach. If we want to _thank_ specific
companies, that could/should go into gcc/doc/contrib.texi, I'd say.
> Remove these two paragraphs. I think they come across as alarmist
> (unnecessarily so), since this is no longer a common conception (at least
> as far as I'm concerned).
Absolutely, yes.
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/
next prev parent reply other threads:[~2003-05-16 8:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 14:35 Gerald Pfeifer
2003-05-09 14:52 ` Gabriel Dos Reis
2003-05-09 15:05 ` Michael Matz
2003-05-09 16:55 ` Joe Buck
2003-05-09 18:21 ` Tom Lord
2003-05-09 18:32 ` Tom Lord
2003-05-17 15:21 ` Gerald Pfeifer
2003-05-19 16:36 ` Joe Buck
2003-05-19 21:09 ` Mike Stump
2003-05-09 15:10 ` Russ Allbery
2003-05-16 8:53 ` Gerald Pfeifer [this message]
2003-05-09 18:00 ` DJ Delorie
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.55.0305161049180.9885@acrux.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc@gcc.gnu.org \
--cc=rra@stanford.edu \
/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).