From: "Navin Johnson" <navin.r.j@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] Non-technical discussions on 9fans
Date: Fri, 23 Nov 2007 09:13:40 +0900 [thread overview]
Message-ID: <b7ec34790711221613n13237e1bie1ba283ae14ac402@mail.gmail.com> (raw)
On Nov 23, 2007 12:44 AM, Russ Cox <rsc@swtch.com> wrote:
> > Does anyone see any merit in having a stacked mailing list? For
>
> what i'd like is to have a mailing list i can subscribe to
> that is 9fans with just the technical content and none of
> the whining. (so this message wouldn't make it through.)
I have two sincere questions for the community.To where should we move
non-technical discussions? Would creating a '9fans-adm" for this
purpose be worthwhile?
To save you time in apparently pointless rhetoric, I've created
"9fans-adm@googlegroups.com".
Kindly consider moving non-technical Plan 9 related discussions here.
-navin
reply other threads:[~2007-11-23 0:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b7ec34790711221613n13237e1bie1ba283ae14ac402@mail.gmail.com \
--to=navin.r.j@gmail.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).