From: Larry McVoy <lm@mcvoy.com>
To: Norman Wilson <norman@oclsc.org>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] SCCS
Date: Fri, 13 Sep 2019 14:51:27 -0700 [thread overview]
Message-ID: <20190913215127.GG2046@mcvoy.com> (raw)
In-Reply-To: <1568410636.21547.for-standards-violators@oclsc.org>
On Fri, Sep 13, 2019 at 05:37:12PM -0400, Norman Wilson wrote:
> The actual basis for that opinion (and it's just my opinion but it's
> not pulled out of hyperspace) is that the older systems think only
> about one file at a time, not collections of files.
Yep. That's the problem that BitKeeper solved first, correctly, with
atomic commits, full rename tracking, etc. If you googled "changeset"
back in 1996 before BitKeeper started happening there were 6 hits
(mostly for a really weird system called Aide De Camp).
If you googled it 5 years later there were millions of hits, almost
100% BitKeeper related.
One of the selling points of BK back in the day was "remember when you
forgot to tag the tree in CVS and you couldn't get back to where you
wanted to be? Yeah, every commit in BK is a tag, you can roll back
to anywhere."
So I agree with you Norm that exact problem was part of why BitKeeper
was invented. When I was going on about SCCS, I was admiring the weave,
it's a neat way to do things. But I wouldn't suggest anyone use just
SCCS today, that's nuts.
next prev parent reply other threads:[~2019-09-13 21:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 21:37 Norman Wilson
2019-09-13 21:51 ` Larry McVoy [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-12 4:25 Jon Steinhart
2019-09-09 6:25 [TUHS] PWB vs Unix/TS Warner Losh
2019-09-10 15:16 ` Clem Cole
2019-09-11 3:53 ` Warner Losh
2019-09-11 15:36 ` Clem Cole
2019-09-11 18:11 ` Larry McVoy
2019-09-11 22:49 ` Dave Horsfall
2019-09-12 3:43 ` [TUHS] SCCS Larry McVoy
2019-09-12 4:20 ` George Michaelson
2019-09-12 4:28 ` Jon Forrest
2019-09-12 4:33 ` Larry McVoy
2019-09-12 6:12 ` William Corcoran
2019-09-12 14:35 ` Clem Cole
2019-09-13 5:22 ` Dave Horsfall
2019-09-13 5:50 ` Bakul Shah
2019-09-12 16:45 ` Eric Allman
2019-09-12 17:29 ` Clem Cole
2019-09-12 17:47 ` Warner Losh
2019-09-13 8:12 ` emanuel stiebler
2019-09-13 21:11 ` Steffen Nurpmeso
2019-09-13 21:17 ` Larry McVoy
2019-09-13 21:48 ` Bakul Shah
2019-09-13 23:12 ` Steffen Nurpmeso
2019-09-13 23:03 ` Steffen Nurpmeso
2019-09-14 1:55 ` [TUHS] [SPAM] SCCS Larry McVoy
2019-09-16 17:23 ` [TUHS] SCCS Steffen Nurpmeso
2019-09-16 20:31 ` Larry McVoy
2019-09-17 17:57 ` Steffen Nurpmeso
2019-09-18 8:48 ` Eric Allman
2019-09-18 17:33 ` Steffen Nurpmeso
2019-09-12 20:07 ` Nemo
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=20190913215127.GG2046@mcvoy.com \
--to=lm@mcvoy.com \
--cc=norman@oclsc.org \
--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).