From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu, plan9changes@googlegroups.com
Subject: Re: [9fans] Notice: plan9changes will not receive updates until 20th of May
Date: Sat, 6 May 2006 17:48:21 -0500 [thread overview]
Message-ID: <4ce3c0b6e7e386a1c0909114a333ab5d@swtch.com> (raw)
In-Reply-To: <5d375e920605061423m49a9e277x50b59abba085c6e4@mail.gmail.com>
> There will be no new posts until the 20th of May, the server that runs the
> scripts that generate change/patch notifications are on a ADSL line that will
> be down until I come back from a trip. My apologies for the inconvenience.
>
> If you would like to see the scripts moved to the Bell Labs servers that host
> the main sources repository so this doesn't happen again, please email
> rsc@swtch.com and try to convince Russ to do it (my emails to him about
> this did not receive any real answer.)
I stopped writing change entries two weeks ago. It was very liberating.
Russ
prev parent reply other threads:[~2006-05-06 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 21:23 Uriel
2006-05-06 21:44 ` Francisco J Ballesteros
2006-05-06 22:48 ` Russ Cox [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=4ce3c0b6e7e386a1c0909114a333ab5d@swtch.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
--cc=plan9changes@googlegroups.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).