From: doug@cs.dartmouth.edu (Doug McIlroy)
Subject: [TUHS] Transcribing and simulating PDP-7 Unix
Date: Thu, 25 Feb 2016 23:21:06 -0500 [thread overview]
Message-ID: <201602260421.u1Q4L6P6026620@tahoe.cs.Dartmouth.EDU> (raw)
> Norman Wilson is going to try and get us some higher quality scans which
will help a great deal in deciphering some of the hard to read characters.
A second scan, high or low quality, is a tremendous help. Diffing them
is a really good way to spot trouble.
Doug
next reply other threads:[~2016-02-26 4:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 4:21 Doug McIlroy [this message]
[not found] <CAAFR5pZXe2Oy8Pv_K_SPNnZrU2+jtBtDwx+gGx=RcRDfRk9Umw@mail.gmail.com>
2016-02-25 19:56 ` Warren Toomey
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=201602260421.u1Q4L6P6026620@tahoe.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.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).