From: John Cowan <cowan@ccil.org>
To: Rob Pike <robpike@gmail.com>
Cc: Bakul Shah <bakul@iitbombay.org>, TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] v7 source code for sh
Date: Sat, 19 Feb 2022 17:39:55 -0500 [thread overview]
Message-ID: <CAD2gp_S9-dNELkAMUG0YJpy9y46T=JBzvHcHf4-FqPahUAJqbQ@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgzn8V2zykc-NtVW=Kgz62vtRwmtQD7u_mGf6U=b6VXJtA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
On Sat, Feb 19, 2022 at 1:45 PM Rob Pike <robpike@gmail.com> wrote:
> I undid all the macros for the v8 shell, with Steve's blessing, before
> doing the key work on that shell. But no one outside cared about any of the
> research Unixes after v7,
>
Lots of us would have loved to care about them and were sad that we
couldn't until they were open sourced much later.
[-- Attachment #2: Type: text/html, Size: 913 bytes --]
next prev parent reply other threads:[~2022-02-19 22:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 17:44 Bakul Shah
2022-02-19 18:44 ` Rob Pike
2022-02-19 19:29 ` Clem Cole
2022-02-19 22:39 ` John Cowan [this message]
2022-02-19 23:11 ` Sven Mascheck
2022-02-19 23:34 ` Rob Pike
2022-02-19 23:36 ` silas poulson
2022-02-20 20:54 ` Chet Ramey
2022-02-20 21:02 ` Larry McVoy
2022-02-20 21:19 ` Chet Ramey
2022-02-20 21:19 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-02-20 22:39 ` Chet Ramey
2022-02-21 1:01 ` Dan Cross
2022-02-22 4:54 ` Dan Stromberg
2022-02-22 5:39 ` Rob Pike
2022-02-22 5:54 ` George Michaelson
-- strict thread matches above, loose matches on Subject: below --
2022-02-22 3:07 Brian Walden
2022-02-22 14:28 ` Chet Ramey
2022-02-22 14:47 ` Clem Cole
2022-02-21 17:58 Norman Wilson
2022-02-21 18:10 ` Rob Pike
2022-02-20 7:24 Rudi Blom
2022-02-19 15:43 Will Senn
2022-02-19 16:03 ` Steve Nickolas
2022-02-19 16:07 ` Clem Cole
2022-02-19 16:43 ` Steve Nickolas
2022-02-19 17:24 ` Ron Natalie
2022-02-19 16:04 ` Clem Cole
2022-02-19 16:06 ` Bakul Shah
2022-02-19 16:57 ` Will Senn
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='CAD2gp_S9-dNELkAMUG0YJpy9y46T=JBzvHcHf4-FqPahUAJqbQ@mail.gmail.com' \
--to=cowan@ccil.org \
--cc=bakul@iitbombay.org \
--cc=robpike@gmail.com \
--cc=tuhs@minnie.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).