From: suspect <suspect@research.suspicious.org>
To: <9fans@cse.psu.edu>
Subject: [9fans] GCC
Date: Thu, 8 Nov 2001 09:45:55 -0500 [thread overview]
Message-ID: <Pine.BSO.4.33L2.0111080941390.13834-100000@spy.suspicious.org> (raw)
In-Reply-To: <20011107185604.2664B199F3@mail.cse.psu.edu>
On Wed, 7 Nov 2001, David Gordon Hogan wrote:
>
> No, it's a symptom of ``I wasted weeks of my life struggling
> with this awful code''.
Amidst all this clamor, I must ask: Why did you take the time to port
GCC ? Was it done under duress ?
-
next prev parent reply other threads:[~2001-11-08 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 18:56 [9fans] Rant (was Re: Plan9 and Ada95?) David Gordon Hogan
2001-11-07 19:33 ` Lucio De Re
2001-11-08 1:43 ` Dan Cross
2001-11-08 14:45 ` suspect [this message]
2001-11-29 5:01 ` Boyd Roberts
2013-03-24 2:45 [9fans] gcc Winston Kodogo
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.BSO.4.33L2.0111080941390.13834-100000@spy.suspicious.org \
--to=suspect@research.suspicious.org \
--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).