From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] INVESTMENT & ASSISTANCE
Date: Tue, 18 Jun 2002 02:06:50 -0400 [thread overview]
Message-ID: <ac35a999dec57ba6bd2d84c9b92714ee@plan9.bell-labs.com> (raw)
> Unfortunately (but maybe not) you're right, the mail<->news gateway
> would fail. Again, that does not bother me, as I have no NetNews
> access and prefer closed mailing lists anyway, but others will
> understandably differ in opinion.
Other things would break too. For example most of the readers
on plan9.bell-labs.com aren't subscribed directly.
We have a local fan-out address that is subscribed.
And I should be able to post from any of my addresses,
etc. etc. etc.
next reply other threads:[~2002-06-18 6:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 6:06 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-17 1:45 Russ Cox
2002-06-17 1:28 presotto
[not found] <20020616170512.14978199BB@mail.cse.psu.edu>
2002-06-16 21:12 ` Digby Tarvin
2002-06-17 0:49 ` Scott Schwartz
2002-06-18 5:23 ` Lucio De Re
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=ac35a999dec57ba6bd2d84c9b92714ee@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).