The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] Reorganising the Unix Archive?
Date: Sat, 18 Feb 2017 14:40:57 +1000	[thread overview]
Message-ID: <16138E23-BFB8-47F8-B41B-2D2AE8DD8F46@tuhs.org> (raw)
In-Reply-To: <201702180330.v1I3UCHj018425@coolidge.cs.Dartmouth.EDU>

That's what the Unix Tree is for!
http://minnie.tuhs.org/UnixTree
Also, Diomidis' Github repository
https://github.com/dspinellis/unix-history-repo

Cheers, Warren

On 18 February 2017 1:30:12 pm AEST, Doug McIlroy <doug at cs.dartmouth.edu> wrote:
>If things are filed by provenance, one useful kind of
>cross-linking would be a generic tree whose "leaves"
>link to all the versions of the "same" file. All the
>better if it could also indicate the degree of
>relatedness of the versions--perhaps an inferred
>evolutionary tree or a shaded grid, where the
>intensity of grid point x,y shows the relatedness
>of x and y.
>
>doug

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170218/bf93b320/attachment.html>


  reply	other threads:[~2017-02-18  4:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-18  3:30 Doug McIlroy
2017-02-18  4:40 ` Warren Toomey [this message]
2017-02-18 17:19   ` Random832
  -- strict thread matches above, loose matches on Subject: below --
2017-02-19  0:12 Doug McIlroy
2017-02-20  1:48 ` William Corcoran
2017-02-20  2:33   ` Doug McIlroy
2017-02-20  2:52     ` Larry McVoy
2017-02-20 18:06   ` Joerg Schilling
2017-02-18 18:49 Doug McIlroy
2017-02-18  0:12 Warren Toomey
2017-02-18  0:21 ` Warren Toomey
2017-02-18  0:40 ` Clem Cole
2017-02-18  1:09   ` Warren Toomey
2017-02-18 17:17 ` Random832

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=16138E23-BFB8-47F8-B41B-2D2AE8DD8F46@tuhs.org \
    --to=wkt@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).