From: "Michael Kjörling" <e5655f30a07f@ewoof.net>
To: tuhs@tuhs.org
Subject: [TUHS] Re: early Unix papers, from jim Joyce
Date: Wed, 2 Nov 2022 07:32:45 +0000 [thread overview]
Message-ID: <a99aa467-869c-49df-9d3c-57747247e6bf@home.arpa> (raw)
In-Reply-To: <20221102060730.A114A18C08A@mercury.lcs.mit.edu>
On 2 Nov 2022 02:07 -0400, from jnc@mercury.lcs.mit.edu (Noel Chiappa):
>> Suggestions?
>
> Step #0: make a list of what's there, and post it here. That's crucial input
> to any recommendation.
Agreed.
Also, step #1: Before sending them off somewhere or tossing them,
consider whether some place like the Computer History Museum might be
interested in them.
--
🪶 Michael Kjörling 🏡 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
next prev parent reply other threads:[~2022-11-02 7:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 3:46 [TUHS] early Unix papers, from Jim Joyce Rich Morin
2022-11-02 6:07 ` [TUHS] " Noel Chiappa
2022-11-02 7:32 ` Michael Kjörling [this message]
2022-11-02 15:32 ` Grant Taylor via TUHS
2022-11-06 23:56 ` Rich Morin
2022-11-07 22:16 ` Grant Taylor via TUHS
2022-11-07 23:12 ` segaloco via TUHS
2022-11-08 6:30 ` arnold
2022-11-08 22:56 ` James Frew
2022-11-08 16:42 ` G. Branden Robinson
2022-11-17 20:42 Rich Morin
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=a99aa467-869c-49df-9d3c-57747247e6bf@home.arpa \
--to=e5655f30a07f@ewoof.net \
--cc=tuhs@tuhs.org \
/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).