The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] PWB contributions
Date: Sun, 8 Nov 2015 20:44:08 -0800	[thread overview]
Message-ID: <20151109044407.GD22320@mcvoy.com> (raw)
In-Reply-To: <201511090139.tA91dCvK006536@coolidge.cs.Dartmouth.EDU>

On Sun, Nov 08, 2015 at 08:39:12PM -0500, Doug McIlroy wrote:
> >> I thought PWB (makers of "make") came from Harvard?
> 
> > PWB ...  came straight out of Bell. Not sure about all the
> > applications (well, SCCS came from Bell).
> 
> PWB did not create make; Stu Feldman did it in research.
> PWB did make SCCS. 

Marc Rochkind did SCCS, right?  Wikipedia said he did it at Bell Labs.

Does anyone on the list remember him?  I'd love to hear some stories
about how SCCS was created.

Warning: source management rant coming.

SCCS got a bad rap from Walter Tichy when he created RCS, I can't remember
his dislike but it's completely wrong.  RCS is diff based, you have a file
and a series of patches.  For the tip of the trunk, that's the file, going
backwards in history they are reverse patches.  OK, not so crazy.  But now
think about a branch.  You do reverse patches back to the branch point and
forward patches down to the tip of the branch.  Anyone living on a branch
hated RCS.

SCCS has interleaved deltas.   It's a brilliant design that has far far
better performance than anything else out there.  I'll explain that if
anyone cares but I'd love to know if anyone talked to Marc while he was
building SCCS.  Love to learn how he came up with that.

The reason I know so much about SCCS is that BitKeeper is sort of SCCS 
on steroids, we took the file format, fixed a bunch of stuff, and made
the first distributed version control system with it.  Git, Mercurial,
all the others, are copies of what we did.

I wish Marc was on this list, be fun to chat.

--lm



  parent reply	other threads:[~2015-11-09  4:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09  1:39 Doug McIlroy
2015-11-09  1:48 ` John Cowan
2015-11-09  2:12 ` Clement T. Cole
2015-11-09  2:54   ` Win Treese
2015-11-09  2:58     ` Win Treese
2015-11-09  3:36       ` Clem cole
2015-11-09  3:51         ` Clem cole
2015-11-09 15:40         ` Dave Horsfall
2015-11-09 15:54           ` Clem Cole
2015-11-09 22:12         ` Mary Ann Horton
2015-11-09  3:38       ` Random832
2015-11-09  4:50         ` Clem cole
2015-11-09 13:58   ` Doug McIlroy
2015-11-09 14:02     ` Ronald Natalie
2015-11-09 14:44     ` John Cowan
2015-11-10 20:26     ` [TUHS] A portrait of cut(1) (was: PWB contributions) markus schnalke
2015-11-10 22:10       ` Clem Cole
2015-11-10 23:10       ` Andy Kosela
2015-11-10 23:12         ` John Cowan
2015-11-10 23:34           ` Larry McVoy
2015-11-10 23:39             ` John Cowan
2015-11-11  0:16       ` [TUHS] A portrait of cut(1) Random832
2015-11-11 12:23         ` markus schnalke
2015-11-09 22:23   ` [TUHS] PWB contributions Jeremy C. Reed
2015-11-10  4:11     ` Random832
2015-11-09  4:44 ` Larry McVoy [this message]
2015-11-09  4:51   ` John Cowan
2015-11-09  5:07     ` Larry McVoy
2015-11-09  5:09       ` Larry McVoy
2015-11-09  5:16         ` John Cowan
2015-11-09  5:16         ` Leonardo Taccari
2015-11-09  2:14 Doug McIlroy
2015-11-09  2:32 ` John Cowan

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=20151109044407.GD22320@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).