From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Bell Labs Computer Science Technical Reports
Date: Tue, 21 Mar 2017 15:55:14 -0700 [thread overview]
Message-ID: <20170321225514.GO7783@mcvoy.com> (raw)
In-Reply-To: <20170321202950.GA14540@minnie.tuhs.org>
On Wed, Mar 22, 2017 at 06:29:50AM +1000, Warren Toomey wrote:
> > However, I'm wondering whether we should/could do something to also archive
> > the actual pages of all the Bell Labs Computer Science Technical Reports. I
> > think some are the only authoritative primary source for many Unix-related
> > gems and a lack of an electronic archive means they will slowly fade into
> > non-existence. I remember we had many of those at the library of Imperial
> > College London. Any suggestions on what we can do to archive this material?
>
> I've got the Unix-related BSTJ articles at
> http://www.tuhs.org/Archive/Documentation/Papers/BSTJ/
As a troff fan, I'd *love* to see the original sources. I bet anything
they roff just fine today.
next prev parent reply other threads:[~2017-03-21 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 17:38 Diomidis Spinellis
2017-03-21 20:29 ` Warren Toomey
2017-03-21 22:55 ` Larry McVoy [this message]
2017-03-22 1:31 ` Toby Thain
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=20170321225514.GO7783@mcvoy.com \
--to=lm@mcvoy.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).