From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Browser
Date: Fri, 21 Jun 2002 08:54:34 -0400 [thread overview]
Message-ID: <Pine.LNX.4.30.0206210852490.7320-100000@athena> (raw)
In-Reply-To: <787621fdfbc1a1174d888fbc719eeb4a@plan9.bell-labs.com>
hehe,
Something tells me responding, "somewhere between these
two orders of magnitude," might not impress them terribly
much ... but hey, you ask for a ballpark figure, you
can't be surprised when that's what you get.
;)
sam
On Fri, 21 Jun 2002 presotto@plan9.bell-labs.com wrote:
> 200 < x < 2000
next prev parent reply other threads:[~2002-06-21 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 13:27 presotto
2002-06-21 12:54 ` Sam [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-21 13:33 rob pike, esq.
2002-06-21 12:50 ` Sam
2002-06-21 12:14 Sam
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.LNX.4.30.0206210852490.7320-100000@athena \
--to=sah@softcardsystems.com \
--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).