9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9fans archive
Date: Mon, 12 Jun 2000 18:06:12 -0400	[thread overview]
Message-ID: <20000612220612.4220.qmail@g.bio.cse.psu.edu> (raw)
In-Reply-To: Message from Richard Uhtenwoldt <ru@ohio.river.org> of "Mon, 12 Jun 2000 14:41:22 PDT." <200006122141.OAA27743@ohio.river.org>

Richard says:
> the old home of the archives of the 9fans mailing list is unreachable,

Everything should be available from
	http://www.cse.psu.edu/~schwartz/9fans/archives

If there's a problem, please let me know.  (The filenames aren't y2k
compliant; blame majordomo.)

On that score, I've been getting lots of bounces from demon.net.  Folks
who get 9fans via them might want to check the archives for recent
traffic that didn't make it.



  reply	other threads:[~2000-06-12 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ru@ohio.river.org>
2000-06-12 21:41 ` Richard Uhtenwoldt
2000-06-12 22:06   ` Scott Schwartz [this message]
2000-11-27 16:47 rog
2000-11-27 20:11 ` Scott Schwartz

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=20000612220612.4220.qmail@g.bio.cse.psu.edu \
    --to=schwartz@bio.cse.psu.edu \
    --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).