From: b4@gewt.net (Cory Smelosky)
Subject: [TUHS] UUCP Recreation Network
Date: Wed, 08 Mar 2017 19:47:34 -0800 [thread overview]
Message-ID: <1489031254.1831772.905356984.7FA4DE49@webmail.messagingengine.com> (raw)
In-Reply-To: <20170309034333.GA14730@minnie.tuhs.org>
On Wed, Mar 8, 2017, at 19:43, Warren Toomey wrote:
> On Wed, Mar 08, 2017 at 07:34:46PM -0800, Cory Smelosky wrote:
> > What means of interconnection are we going to use?
> > A map/list of interconnections would be nice. Need a central database
> > somewhere.
>
> https://github.com/DoctorWkt/4bsd-uucp/blob/master/uucp_sites.txt
> for now, it can be improved.
>
> Warren
> Email had 1 attachment:
> + signature.asc
> 1k (application/pgp-signature)
Hmmm. I might markdown-ify that and see if it can go on a github wiki
page.
Looks like we're using 5000 for external? put me at sj.gewt.net:5000
--
Cory Smelosky
b4 at gewt.net
next prev parent reply other threads:[~2017-03-09 3:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 3:34 Cory Smelosky
2017-03-09 3:43 ` Warren Toomey
2017-03-09 3:47 ` Cory Smelosky [this message]
2017-03-09 3:51 ` Erik E. Fair
2017-03-09 9:20 ` Dave Horsfall
2017-03-09 14:20 ` John Floren
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=1489031254.1831772.905356984.7FA4DE49@webmail.messagingengine.com \
--to=b4@gewt.net \
/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).