From: Alan Watson <alan@oldp.astro.wisc.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: rc FAQ list
Date: Sat, 4 Sep 1993 14:46:39 -0400 [thread overview]
Message-ID: <9309041846.AA11931@oldp.astro.wisc.edu> (raw)
Coming to a news feed near you. Multiple times, in fact. There's
nothing quite like screwing up before an audience of thousands of your
peers when it comes to putting a crimp in your day, is there?
I'll be making future (single) postings on or around the 5th of each
month.
The major difference between this version and the last is that the
heterogeneous cluster section has become more sane
Thanks to everyone who helped get this of the ground,
Alan.
next reply other threads:[~1993-09-04 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-09-04 18:46 Alan Watson [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-07-25 3:06 Alan Watson
1993-07-25 0:44 Alan Watson
1993-07-25 1:16 ` Scott Schwartz
1993-07-26 9:33 ` Richard Brooksby
1993-07-26 9:58 ` Tim.Goodwin
1993-07-25 2:36 ` Dennis Colarelli
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=9309041846.AA11931@oldp.astro.wisc.edu \
--to=alan@oldp.astro.wisc.edu \
--cc=rc@hawkwind.utcs.toronto.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).