From: geoff@plan9.cs.su.oz.au geoff@plan9.cs.su.oz.au
Subject: comp.os.plan9
Date: Sun, 6 Feb 1994 12:15:59 -0500 [thread overview]
Message-ID: <19940206171559.ovbrOjOboqpluncAi0-JLIky0xJpEAhwy3jaS7VGjqg@z> (raw)
Alas, that was my call; I've put the RFD for comp.os.plan9
out a couple of times. The first time I couldn't really
follow it up, as thesis work intervened. Both times the
response didn't justify proceeding to a vote. I had a number
of enthusiatic responses via e-mail - but you need 100 more
YES votes than NO votes, and there's a hard core of people who
vote NO to everything that they aren't personally interested.
I didn't want the group to fail, and I don't want to create an
alt group (given that Plan 9 really does deserve it's own Big
7 group). I figure I'll wait until after USENIX before bringing
it up; who knows? If the folks from Bell publish Plan 9, then
we'll probably have trouble _not_ getting a comp.os.plan9 - look
at the interest in that astoundingly mediocre and uninteresting
Linux thing.
Geoff.
next reply other threads:[~1994-02-06 17:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-02-06 17:15 geoff [this message]
1994-02-06 19:46 comp.os.plan9 Vijay
1994-02-07 0:21 comp.os.plan9 Scott
1995-03-30 18:32 comp.os.plan9 Geoff
1995-03-31 14:14 comp.os.plan9 Dirk
1995-03-31 22:56 comp.os.plan9 Jim
1995-04-01 1:08 comp.os.plan9 Bill
1995-04-01 1:15 comp.os.plan9 rob
1995-04-01 3:59 comp.os.plan9 rob
1995-04-01 11:28 comp.os.plan9 Martin
1995-04-01 11:36 comp.os.plan9 Harald
1995-04-01 20:48 comp.os.plan9 Geoff
1995-04-01 21:38 comp.os.plan9 Gregg
1995-04-02 0:29 comp.os.plan9 Scott
1995-04-03 0:58 comp.os.plan9 Christopher.Vance
1995-04-04 7:30 comp.os.plan9 Hans-Peter
1995-08-01 17:27 comp.os.plan9 Jim
1995-08-28 8:27 comp.os.plan9 dhog
1995-08-28 9:19 comp.os.plan9 forsyth
1995-08-28 9:33 comp.os.plan9 Kiran
1995-08-28 13:45 comp.os.plan9 Scott
1995-08-28 16:30 comp.os.plan9 Steven
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=19940206171559.ovbrOjOboqpluncAi0-JLIky0xJpEAhwy3jaS7VGjqg@z \
--to=geoff@plan9.cs.su.oz.au \
/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).