The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Diomidis Spinellis <dds@aueb.gr>
To: Rob Pike <robpike@gmail.com>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: forgotten versions
Date: Fri, 17 Jun 2022 10:20:59 +0300	[thread overview]
Message-ID: <1cd0c358-256a-4636-3019-20fddbee2ff6@aueb.gr> (raw)
In-Reply-To: <CAKzdPgytk74NekqE1gj2jjDAiKfRSONjuad3gSrZToQCwHmE3g@mail.gmail.com>

It is indeed problematic that the Unix history repository is missing the 
Research Editions.  At the time I created it, the source code of the 
Research Unix Eighth and Ninth Editions wasn't openly available.  I'm 
now discussing with another member of this list for a pull request to 
add them.  Incorporating them properly isn't trivial, because various 
mappings are needed to establish authorship information and to allow 
git-blame to work across snapshots of moved files.

Diomidis - https://www.spinellis.gr/

On 17-Jun-22 2:06, Rob Pike wrote:
> Excited as I was to see this history of Unix code in a single repository:
> 
> https://github.com/dspinellis/unix-history-repo 
> <https://github.com/dspinellis/unix-history-repo>
> 
> it continues the long-standing tradition of ignoring all the work done 
> at Bell Labs after v7. I consider v8 v9 v10 to be worth of attention, 
> even influential, but to hear this list talk about it - or discussions 
> just about anywhere else - you'd think they never existed. 

  parent reply	other threads:[~2022-06-17  7:21 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 23:06 [TUHS] " Rob Pike
2022-06-16 23:17 ` [TUHS] " Earl Baugh
2022-06-16 23:18 ` George Michaelson
2022-06-16 23:44   ` George Michaelson
2022-06-17  0:10     ` Larry McVoy
2022-06-17 16:23     ` [TUHS] Sockets vs Streams (was " Bakul Shah
2022-06-17 17:43       ` [TUHS] " Paul Winalski
2022-06-17 22:52       ` Dan Stromberg
2022-06-17  7:20 ` Diomidis Spinellis [this message]
2022-06-17  7:33   ` [TUHS] " Rob Pike
2022-06-17  8:34   ` arnold
2022-06-17 10:52 ` arnold
2022-06-18  7:05 ` Angelo Papenhoff
2022-06-19  7:50   ` Rob Pike
2022-06-19  8:17     ` Angelo Papenhoff
2022-06-19  8:53       ` Rob Pike
2022-06-19  9:02         ` Angelo Papenhoff
2022-06-19  9:14           ` arnold
2022-06-19  9:19             ` Angelo Papenhoff
2022-06-19  9:23               ` arnold
2022-06-19 11:37                 ` Matthias Bruestle
2022-06-19 14:47         ` Kenneth Goodwin
2022-06-19 16:27           ` Al Kossow
2022-06-19 18:32           ` Theodore Ts'o
2022-06-19 18:38             ` Dan Cross
2022-06-21 23:56               ` Jacob Moody
2022-06-22  0:13                 ` Larry McVoy
2022-06-22  0:48                   ` Rob Pike
2022-06-22  1:55                     ` George Michaelson
2022-06-22  2:10                       ` Bakul Shah
2022-06-22  2:14                       ` Jon Steinhart
2022-06-22  2:19                         ` Andrew Hume
2022-06-22  2:58                           ` Rob Pike
2022-06-22  3:09                             ` George Michaelson
2022-06-22  2:16                   ` Andrew Hume
2022-06-22  2:55                   ` Brad Spencer
2022-06-17 14:50 Paul Ruizendaal
2022-06-18  0:35 Douglas McIlroy
2022-06-18  5:00 ` Kevin Bowling
2022-06-18  5:13   ` Adam Thornton
2022-06-18 16:58     ` Clem Cole
2022-06-18 17:18       ` Warner Losh
2022-06-18 17:57         ` Clem Cole
2022-06-18 19:55 Paul Ruizendaal
2022-06-22 12:06 Noel Chiappa
2022-06-23  0:02 ` Dan Cross
2022-06-23  2:18 Noel Chiappa
2022-06-24  6:47 Paul Ruizendaal
2022-06-25 19:16 ` Anthony Martin
2022-06-25 20:45   ` Paul Ruizendaal
2022-06-27  0:57     ` Kevin Bowling

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=1cd0c358-256a-4636-3019-20fddbee2ff6@aueb.gr \
    --to=dds@aueb.gr \
    --cc=robpike@gmail.com \
    --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).