From: Bruce Ellis <brucee@chunder.com>
To: Eric Van Hensbergen <ericvh@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: [plan9dev] Re: Cross Post: Update the Wiki with what you are working on
Date: Thu, 14 Oct 2004 00:06:46 +1000 [thread overview]
Message-ID: <416D3676.1080701@chunder.com> (raw)
In-Reply-To: <a4e6962a04101305535d6bea43@mail.gmail.com>
>> However, 9fans is more of a users-list while 9dev is intended as more
>> of a developer's list with a lower S/N ratio.
Well get that S/N lower and we won't have to bother. I thought 1:1
was fine but clearly you can beat whatever you are at now by only
posting noise ...
As I have just done.
brucee
prev parent reply other threads:[~2004-10-13 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 14:00 [9fans] " Eric Van Hensbergen
[not found] ` <1097559818.303604.164580@c13g2000cwb.googlegroups.com>
[not found] ` <a4e6962a041012054640f69473@mail.gmail.com>
[not found] ` <1097632215.318997.237640@f14g2000cwb.googlegroups.com>
2004-10-13 12:53 ` [9fans] Re: [plan9dev] " Eric Van Hensbergen
2004-10-13 14:06 ` Bruce Ellis [this message]
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=416D3676.1080701@chunder.com \
--to=brucee@chunder.com \
--cc=9fans@cse.psu.edu \
--cc=ericvh@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).