From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Is this a bug in 8c?
Date: Fri, 15 Mar 2002 11:52:50 +0000 [thread overview]
Message-ID: <20020315115533.77C4319A8B@mail.cse.psu.edu> (raw)
>>Wow, the snide self-superiority of the previous conversation is really
>>coming home to roost.
i don't think anyone was snide, or even self-superior.
we just don't think gcc is the alpha and omega of compilers,
or even that the trade-offs make sense everywhere.
give it a rest.
next reply other threads:[~2002-03-15 11:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 11:52 forsyth [this message]
2002-03-15 16:53 ` Thomas Bushnell, BSG
2002-03-15 17:53 ` William Josephson
-- strict thread matches above, loose matches on Subject: below --
2002-03-15 16:41 Fco.J.Ballesteros
2002-03-15 14:43 bwc
2002-03-15 14:11 Russ Cox
2002-03-15 14:08 Russ Cox
2002-03-15 13:51 rob pike
2002-03-15 17:26 ` Thomas Bushnell, BSG
2002-03-15 11:52 forsyth
2002-03-14 19:43 Russ Cox
2002-03-14 19:49 ` Martin Harriss
2002-03-15 10:18 ` Thomas Bushnell, BSG
2002-03-15 10:19 ` Douglas A. Gwyn
2002-03-14 19:20 bwc
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=20020315115533.77C4319A8B@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.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 NNTP newsgroup(s).