From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Cc: 9fans@collyer.net
Subject: Re: [9fans] Plan 9 Usenix BOF, 12 June 2003
Date: Mon, 16 Jun 2003 17:51:12 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0306161750330.25941-100000@maxroach.lanl.gov> (raw)
In-Reply-To: <a89b7388aa862508e4a9a73b9572dc0f@collyer.net>
I think the big excitement was the announcement that Plan 9 is going to be
open source. This opens it up to manuy new users that could not touch it
before. Great news.
ron
next prev parent reply other threads:[~2003-06-16 23:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 23:43 Geoff Collyer
2003-06-16 23:51 ` ron minnich [this message]
2003-06-17 2:24 ` Russ Cox
2003-06-17 3:22 ` northern snowfall
2003-06-17 2:39 ` Russ Cox
2003-06-17 3:39 ` northern snowfall
2003-06-18 0:45 ` Geoff Collyer
2003-06-18 0:53 ` George Michaelson
2003-06-18 5:53 ` boyd, rounin
2003-06-18 1:08 ` [9fans] " Jim Choate
2003-06-18 1:06 ` David Presotto
2003-06-18 1:09 ` Dan Cross
2003-06-17 17:54 [9fans] " Todd C. Miller
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.44.0306161750330.25941-100000@maxroach.lanl.gov \
--to=rminnich@lanl.gov \
--cc=9fans@collyer.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).