From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Cc: Russ Cox <russcox@gmail.com>
Subject: Re: [9fans] IBM T42
Date: Mon, 25 Oct 2004 08:46:27 -0600 [thread overview]
Message-ID: <Pine.LNX.4.58.0410250846190.25731@linux.site> (raw)
In-Reply-To: <opsgewbfb93anw4g@tiitl.aprote.com>
On Mon, 25 Oct 2004, Tiit Lankots wrote:
> What's the point of venti on a laptop anyway?
it's heavenly! try it sometime.
ron
next prev parent reply other threads:[~2004-10-25 14:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 4:31 Kenji Okamoto
2004-10-25 4:37 ` Russ Cox
2004-10-25 5:01 ` Kenji Okamoto
2004-10-25 5:04 ` Kenji Okamoto
2004-10-25 6:00 ` Tiit Lankots
2004-10-25 8:07 ` Charles Forsyth
2004-10-26 14:21 ` rog
2004-10-26 16:13 ` Tiit Lankots
2004-10-26 16:21 ` Ronald G. Minnich
2004-10-26 17:32 ` Tiit Lankots
2004-10-26 17:43 ` rog
2004-10-26 23:43 ` Heiko Dudzus
2004-10-26 23:18 ` Heiko Dudzus
2004-10-25 14:46 ` Ronald G. Minnich [this message]
2004-10-25 6:21 YAMANASHI Takeshi
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.58.0410250846190.25731@linux.site \
--to=rminnich@lanl.gov \
--cc=9fans@cse.psu.edu \
--cc=russcox@gmail.com \
/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).