From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sources?
Date: Sun, 23 May 2004 13:50:28 -0400 [thread overview]
Message-ID: <992f054980d054adf051795027a7022a@plan9.bell-labs.com> (raw)
In-Reply-To: <ee9e417a04052309411888a782@mail.gmail.com>
it should be back now. my fault, i had to interrupt service to
replace a battery in the uninterruptible power supply to which it
is attached and forgot to turn it back on as it wasn't physically
with the other systems on that ups.
--jim
On Sun May 23 12:41:29 EDT 2004, russcox@gmail.com wrote:
> > is it me or sources is down?
>
> sources is down. should be back up sometime today or tomorrow.
> sorry.
>
> russ
next prev parent reply other threads:[~2004-05-23 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-23 16:08 dvd
2004-05-23 16:41 ` Russ Cox
2004-05-23 17:50 ` jmk [this message]
2004-05-23 19:58 ` Thomas Miller
2015-04-26 16:01 Skip Tavakkolian
2015-04-26 16:07 ` David du Colombier
2015-04-26 17:04 ` Sergey Zhilkin
2015-04-26 17:43 ` steve
2015-04-27 12:18 ` yy
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=992f054980d054adf051795027a7022a@plan9.bell-labs.com \
--to=jmk@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).