From: nao@tom-yam.or.jp (Naoki Hamada)
Subject: [TUHS] Re: Peter H. Salus comments (+32V)
Date: Sun, 19 Oct 2003 23:58:48 +0900 (JST) [thread overview]
Message-ID: <200310191458.h9JEwm58029878@miffy.tom-yam.or.jp> (raw)
In-Reply-To: Dennis Ritchie's message of "Sun, 19 Oct 2003 01:12:01 -0400" <5017f0c843b743ca4605973b364295e5@plan9.bell-labs.com>
Hi,
In message "[TUHS] Re: Peter H. Salus comments (+32V)"
on 03/10/19, Dennis Ritchie <dmr at plan9.bell-labs.com> writes:
>A later poster, nao, asked about London and Reiser's memo
>about their work on what became 32V (TM-78-1353-4).
>This seems to be in the company archives, but not in scanned form.
>I've ordered a paper copy, but the mechanism sometimes
>is a black hole.
I would appreciate it if you would make it available by some means. I
hope it is still nearer than the event horizon of the black hole.
-nao
prev parent reply other threads:[~2003-10-19 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 5:12 Dennis Ritchie
2003-10-19 14:36 ` Kenneth Stailey
2003-10-19 14:58 ` Naoki Hamada [this message]
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=200310191458.h9JEwm58029878@miffy.tom-yam.or.jp \
--to=nao@tom-yam.or.jp \
/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).