The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Claim your early Unix contributions on GitHub
Date: Wed, 30 Mar 2016 20:54:52 -0700	[thread overview]
Message-ID: <20160331035452.GD2940@mcvoy.com> (raw)
In-Reply-To: <56fc645f.kotJtdaWttpw3+f5%schily@schily.net>

On Thu, Mar 31, 2016 at 01:42:23AM +0200, Joerg Schilling wrote:
> Larry McVoy <lm at mcvoy.com> wrote:
> 
> > > Given that using git enforces a loss of meta data, is there a chance to get 
> > > the SCCS history for older UNIX versions?
> >
> > You are the first person outside of BitMover that I've ever seen
> > recognize that.  Go you!  It's very annoying, we can write a perfect BK
> > to Git exporter but going the other way is a research project.
> 
> We talked about this before: You are the only person who does not attack me 
> when I write that SCCS is much faster than RCS, just because you know ;-)

You can thank Walter Tichy, who got a PhD for RCS if I recall, can you
believe that?  He tried to paint SCCS as bad and everyone believed him.

SCCS is brilliant in how it stores the changes, it's a weave rather than
diff and patch.  Which means it can get 1.1 as fast as it can get the tip.
Or better put, in a big tree, it is way way faster than git for some things:

What                      BK              GIT         How much faster is BK?
----------------------------------------------------------------------------
annotate/blame        0.01 seconds     32.3 seconds        3230 times faster
search history        0.01 seconds    138.9 seconds       13890 times faster

That's a 1M changeset tree with 230,000 files (4GB of history).  You all
know what annotate/blame are, the search history is answering the question
"did the string 'those bastards at $COMPANY' ever occur in our source code?"
so it's searching all versions.  The SCCS weave is instant for stuff like 
that; diff and patch have to tons more work.

> The first system to implement something based on previous good ideas was BK and 

We took the weave and turbo charged it.  Recent BK versions are crazy fast.

> AFAIK, GIT was implemented originally as an empty shelf that aimed to imitate 
> the CLI from BK.

No, Git, credit to Linus, was his own ideas.  Yeah, he took the basic model
of clone/pull/commit/push, but the storage format is all his (and retarded,
it doesn't scale, it's all content addressable data by hash, works when it
fits in memory, thrashes like hell when it doesn't).  

Anyhoo, we should take this private, this is a Unix list, not an SCM list.
Though I am loving the work to get a repo, even if it is git, with all
the history.  That's awesome!


  reply	other threads:[~2016-03-31  3:54 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30  7:53 Diomidis Spinellis
2016-03-30 12:31 ` Joerg Schilling
2016-03-30 13:10   ` Diomidis Spinellis
2016-03-30 13:44     ` Joerg Schilling
2016-03-30 19:17   ` Larry McVoy
2016-03-30 21:07     ` Random832
2016-03-30 23:03       ` Joerg Schilling
2016-03-31  3:20       ` Larry McVoy
2016-03-31  3:34         ` Random832
2016-03-31  3:40           ` Larry McVoy
2016-03-30 23:42     ` Joerg Schilling
2016-03-31  3:54       ` Larry McVoy [this message]
2016-03-30 14:25 ` Marc Rochkind
2016-03-30 15:23   ` Joerg Schilling
2016-03-30 19:14     ` Larry McVoy
2016-03-30 15:49   ` Diomidis Spinellis
2016-03-30 16:07     ` Joerg Schilling
2016-03-30 16:29       ` Diomidis Spinellis
2016-03-30 16:14     ` Pat Barron
2016-03-31 21:06       ` Clem Cole
2016-03-31 21:54         ` Ron Natalie
2016-04-01  9:01         ` Diomidis Spinellis
2016-04-01 14:41           ` Clem Cole
2016-04-01 21:00           ` Jeremy C. Reed
2016-04-01 13:06         ` Dave Horsfall
2016-04-01 21:52         ` Pat Barron
2016-03-30 16:30     ` Marc Rochkind
2016-03-30 16:40       ` Joerg Schilling
2016-03-30 16:55       ` John Cowan
2016-03-30 18:28 Norman Wilson
2016-03-30 20:06 ` Ronald Natalie

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=20160331035452.GD2940@mcvoy.com \
    --to=lm@mcvoy.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).