From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] attention - new list address
Date: Fri, 7 Mar 2008 18:58:15 -0500 [thread overview]
Message-ID: <20080307235908.5359B1E8C22@holo.morphisms.net> (raw)
In-Reply-To: <A90163FB-91C3-403C-9A7C-931657DCBA47@mac.com>
> We sign up the usual way?
Everyone who was on 9fans@cse.psu.edu is on 9fans@9fans.net.
There's no need to resubscribe.
They're two separate lists at the moment,
but within a matter of days I expect that
9fans@cse.psu.edu will either stop working
or forward to 9fans@9fans.net.
Either way, it would be best to get in the
habit of mailing 9fans@9fans.net or update
address book entries.
Russ
next prev parent reply other threads:[~2008-03-07 23:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 23:49 Scott Schwartz
2008-03-07 23:51 ` Pietro Gagliardi
2008-03-07 23:58 ` Russ Cox [this message]
2008-03-08 0:10 ` Pietro Gagliardi
2008-03-08 0:28 ` Scott Schwartz
2008-03-10 17:30 ` Dennis Davis
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=20080307235908.5359B1E8C22@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
/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).