From: "Boyd Roberts" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] venti arenas
Date: Wed, 7 May 2003 06:26:16 +0200 [thread overview]
Message-ID: <000801c3147c$c5031680$7b83773e@SOMA> (raw)
In-Reply-To: <20030430111055.I26796@cackle.proxima.alt.za>
From: "Lucio De Re" <lucio@proxima.alt.za>
> That doesn't make a great deal of sense. If it is going to be limited
> to an extra megabyte, why not keep it the exact size and throw the
> remainder away? What does the extra megabyte buy you?
yup:
Always go for overkill -- Lou Reed
--
The Beretta 92FS -- don't leave home without it ...
next prev parent reply other threads:[~2003-05-07 4:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 7:22 nigel
2003-04-30 7:40 ` nigel
2003-04-30 9:03 ` Richard Miller
2003-04-30 9:10 ` Lucio De Re
2003-05-07 4:26 ` Boyd Roberts [this message]
2003-04-30 9:22 ` nigel
2003-04-30 18:10 ` rsc
-- strict thread matches above, loose matches on Subject: below --
2003-04-01 6:34 nigel
2003-04-01 7:47 ` Martin C.Atkins
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='000801c3147c$c5031680$7b83773e@SOMA' \
--to=boyd@insultant.net \
--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).