From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Historical uucp maps?
Date: Thu, 9 Mar 2017 16:45:38 -0500 [thread overview]
Message-ID: <CAC20D2O9Bk9dD2ZfhVZ_mM3226=sYnASQC7K8PJ3LjGyVubbDQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.20.1703100707370.2854@aneurin.horsfall.org>
I was think about your map question, I realized the person you need to rope
in is Ches. He did a lot work mapping the uucp network back in the day.
He even had really cool maps printed up, which I think I might still have
one of them. But he had some really great ones. If he still has them,
those would be great for your 50th.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170309/4a566dbd/attachment.html>
next prev parent reply other threads:[~2017-03-09 21:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 2:33 Norman Wilson
2017-03-09 2:38 ` Warren Toomey
2017-03-09 2:38 ` Ron Natalie
2017-03-09 20:11 ` Dave Horsfall
2017-03-09 21:45 ` Clem Cole [this message]
2017-03-09 2:50 ` Erik E. Fair
2017-03-09 18:37 ` Lyndon Nerenberg
-- strict thread matches above, loose matches on Subject: below --
2017-03-08 22:54 Warren Toomey
2017-03-08 23:10 ` Warren Toomey
2017-03-08 23:24 ` John Floren
2017-03-09 20:00 ` Dave Horsfall
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='CAC20D2O9Bk9dD2ZfhVZ_mM3226=sYnASQC7K8PJ3LjGyVubbDQ@mail.gmail.com' \
--to=clemc@ccc.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).