The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: sdaoden@yandex.com (Steffen Nurpmeso)
Subject: [TUHS] A repository with 44 years of Unix evolution gets the MSR '15 Best Data Showcase Award
Date: Tue, 19 May 2015 15:48:05 +0200	[thread overview]
Message-ID: <20150519134805.5XPp-9sfoaQCoUSbLHeU@yandex.com> (raw)
In-Reply-To: <e8d26052f0632b48fe8c4398ca110f08@xs4all.nl>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]

Jacob Goense <dugo at xs4all.nl> wrote:
 |On 2015-05-19 12:04, Erik E. Fair wrote:
 |> The NetBSD source repository has not changed source control systems
 |> since project inception - we're still using CVS, and the whole thing
 |> can be browsed at anoncvs.netbsd.org. A bunch of stuff is now "in the
 |> attic" (nominally "deleted" from the repository, but so far as I know
 |> that just means it's not fetched by default with an unadorned "get"
 |> command - it's still in the repository archive).
 |> 
 |> The history you're looking to collect is available for copy any time.
 |
 |There is a pile of "revision #.# intentionally removed" in there. See
 |http://www.onlamp.com/pub/a/bsd/2006/09/14/netbsd_future.html?page=2
 |for Hannum's story behind it.
 |
 |Deadly quote "and nobody cares about that early code history any more
 |--so this is all water under the bridge."
 |
 |They are available in a manilla folder through a coughing man in a
 |raincoat if you know in which parking garage you have to look. Not
 |sure what the consequences are if they appear as a pull request for
 |dspinellis's truly awesome unix-history-repo.

I also thought that was bad advise – Jörg Sonnenberger of NetBSD
converted the repository to Fossil.  I have lost that address; he
automatically converts _that_ to git(1) on github [1], which
i track myself, however.

Note that he is the one who is developing the used converter, and
that in turn had some errors in the past, resulting in history to
become invalid.  That didn't happen for quite a while now (afaik!)
but since it was very weird about two years ago and occasionally
happened still last year one possibly should ask him before
integrating all those millions of objects into such a large
repository.

  [1] https://github.com/jsonn/src

--steffen



  reply	other threads:[~2015-05-19 13:48 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 20:07 Diomidis Spinellis
2015-05-19  9:24 ` Tom Ivar Helbekkmo
2015-05-19 10:04   ` Erik E. Fair
2015-05-19 13:19     ` Jacob Goense
2015-05-19 13:48       ` Steffen Nurpmeso [this message]
2015-05-19 14:36         ` SPC
2015-05-19 15:55   ` Warner Losh
2015-05-19 16:48     ` Tom Ivar Helbekkmo
2015-05-19 17:30       ` Clem Cole
2015-05-19 18:06         ` Tom Ivar Helbekkmo
2015-05-19 18:55         ` cowan
2015-05-20  3:07           ` Andy Kosela
2015-05-19 14:53 ` Clem Cole
2015-05-21  1:42 ` Derrik Walker v2.0
2015-05-21 11:50   ` Diomidis Spinellis
2015-05-21 15:09     ` cowan
2015-05-21 15:49       ` Clem Cole
2015-05-21 17:03         ` Jacob Ritorto
2015-05-21 18:04           ` Clem Cole
2015-05-25 16:46             ` Mary Ann Horton
2015-05-25 17:21               ` John Cowan
2015-05-25 21:15               ` Cory Smelosky
2015-05-26 17:55               ` Scot Jenkins
2015-05-29 14:14                 ` Mary Ann Horton
2015-05-22  0:17         ` John Cowan
2015-05-26 19:12   ` Doug McIntyre
2015-05-21 19:54 ` scj
2015-05-19 15:40 Doug McIlroy
2015-05-19 16:26 ` cowan
2015-05-19 17:29   ` Doug McIlroy
2015-05-21 19:41     ` scj
2015-05-25 19:05 Noel Chiappa
2015-05-26 10:07 Berny Goodheart

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=20150519134805.5XPp-9sfoaQCoUSbLHeU@yandex.com \
    --to=sdaoden@yandex.com \
    /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).