From: rmswierczek@gmail.com (Robert Swierczek)
Subject: [TUHS] Non-US Unix Activities
Date: Fri, 7 Apr 2017 13:57:49 -0400 [thread overview]
Message-ID: <CAAFR5pZnmazx8-xLNgJzcEva97aEEP_aOf1Rzd6FWD7GgsSnEw@mail.gmail.com> (raw)
In-Reply-To: <CAFWeb9J6eg6iWWGEtUwJUg9A7uCDVExcXnXNeg9+0WPT4QBmkw@mail.gmail.com>
>> Yes! I am very much interesting in getting my eyes on that early B
>> version of AberMUD (and any other B code for that matter.)
>
>
> It's a few inches thick, I'll dig it out and post sample code photos from
> it, somewhere.
That would be wonderful, but I would really like to bring that
software back to life again. Does anyone know of an inexpensive and
non-labor intensive solution to this? I imagine a fanfold printout
should be fairly easy to scan given the proper scanner. I don't know
how or if the scanner should be taken to Alec's printout or
visa-versa.
I apologize if I sound too eager, but I feel these windows of
opportunity open rarely and then close quick and often permanently.
next prev parent reply other threads:[~2017-04-07 17:57 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 22:22 [TUHS] A decision Warren Toomey
2017-04-06 20:08 ` Josh Good
2017-04-06 20:32 ` Kurt H Maier
2017-04-06 21:23 ` Aram Hăvărneanu
2017-04-06 21:46 ` Josh Good
2017-04-07 11:56 ` Steffen Nurpmeso
2017-04-07 12:20 ` William Corcoran
2017-04-07 14:05 ` Andru Luvisi
2017-04-07 15:09 ` Kurt H Maier
2017-04-07 15:23 ` Larry McVoy
2017-04-07 15:25 ` ron minnich
2017-04-07 20:25 ` Josh Good
2017-04-09 5:57 ` Michaelian Ennis
2017-04-06 23:09 ` [TUHS] Non-US Unix Activities Warren Toomey
2017-04-07 5:15 ` Dave Horsfall
2017-04-07 19:56 ` Dave Horsfall
2017-04-07 8:44 ` Alec Muffett
2017-04-07 9:32 ` Robert Swierczek
2017-04-07 10:24 ` Alec Muffett
2017-04-07 11:35 ` jsteve
2017-04-07 16:09 ` Alec Muffett
2017-04-09 6:34 ` Random832
2017-04-09 11:03 ` Alec Muffett
2017-04-09 16:57 ` Toby Thain
2017-04-09 19:20 ` Random832
2017-04-10 13:06 ` Tim Bradshaw
2017-04-09 22:45 ` Steve Johnson
2017-04-10 5:40 ` Robert Swierczek
2017-04-10 13:10 ` Tim Bradshaw
2017-04-07 17:57 ` Robert Swierczek [this message]
2017-04-07 18:24 ` Toby Thain
2017-04-07 20:23 ` Robert Swierczek
2017-04-07 20:53 ` Toby Thain
2017-04-07 21:51 ` Robert Swierczek
2017-04-07 22:08 ` Steve Johnson
2017-04-07 22:36 ` Larry McVoy
2017-04-07 22:01 ` Alec Muffett
2017-04-08 17:28 ` Lawrence Stewart
2017-04-07 10:40 ` Lars Brinkhoff
2017-04-07 12:09 ` Tim Bradshaw
2017-04-07 12:25 ` jsteve
2017-04-07 13:55 ` tfb
2017-04-07 14:36 ` George Ross
[not found] <mailman.729.1491557525.3779.tuhs@minnie.tuhs.org>
2017-04-07 14:29 ` Arrigo Triulzi
2017-04-07 23:31 Richard Tobin
2017-04-08 10:57 ` Tim Bradshaw
2017-04-08 11:13 ` Jason Stevens
2017-04-08 9:46 Berny Goodheart
2017-04-08 10:28 ` Jason Stevens
2017-04-08 14:31 Doug McIlroy
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=CAAFR5pZnmazx8-xLNgJzcEva97aEEP_aOf1Rzd6FWD7GgsSnEw@mail.gmail.com \
--to=rmswierczek@gmail.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).