From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] "Plan 9 Linux"
Date: Tue, 8 Nov 2005 15:09:19 -0500 [thread overview]
Message-ID: <86c245e86342bddb090761d22a66e722@coraid.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0511081244380.23715@mtdew.lanl.gov>
"Plan 9 comes with everything from a web browser and an IM client, to
multimedia software and an office suite."
that should be added to plan9.bell-labs.com with a footnote
indicating that plan 9 in ambigious and may refer to something
other than bell labs' plan 9, written in 3 pt. type in Anglo-Saxon.
(Unicode is neat!) :)
next prev parent reply other threads:[~2005-11-08 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 14:08 Christoph Lohmann
2005-11-08 15:15 ` John Floren
2005-11-08 15:18 ` Russ Cox
2005-11-08 19:37 ` Crossfire
2005-11-08 19:45 ` andrey mirtchovski
2005-11-08 20:09 ` Brantley Coile [this message]
2005-11-08 15:23 Trickey, Howard W (Howard)
2005-11-08 20:37 Skip Tavakkolian
2005-11-08 21:48 ` andrey mirtchovski
2005-11-08 23:16 ` Devon H. O'Dell
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=86c245e86342bddb090761d22a66e722@coraid.com \
--to=brantley@coraid.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).