The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Warner Losh <imp@bsdimp.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: SCCS roach motel
Date: Fri, 13 Dec 2024 16:53:05 -0800	[thread overview]
Message-ID: <20241214005305.GE11590@mcvoy.com> (raw)
In-Reply-To: <CANCZdfopkKeeerowxDjjBA9ahRnGBPzX4zeoWDFGk4v5J8qmWg@mail.gmail.com>

On Fri, Dec 13, 2024 at 04:38:49PM -0700, Warner Losh wrote:
> On Fri, Dec 13, 2024, 4:19???PM Larry McVoy <lm@mcvoy.com> wrote:
> 
> > On Fri, Dec 13, 2024 at 05:57:55PM -0500, Norman Wilson wrote:
> > > This is verging on COFF material, and I won't mind if someone
> > > moves the discussion thither:
> > >
> > > Clem Cole:
> > >
> > >   As a satisfied user of SCCS (and later Bitkeeper), it's still my
> > preferred
> > >   choice.
> > >
> > > ====
> > >
> > > I have to admit SCCS is one of the many pieces of software
> > > I tried for a week or two > 40 years ago and abandoned because
> > > I couldn't stand it.  I don't think I ever tried RCS, because
> > > I could see it didn't what I saw as the underlying problems.
> > > CVS likewise.  Subversion was the earliest version-control
> > > system that felt usable to me.
> > >
> > > What bugged me so much?  The earlier systems were focussed
> > > entirely (or for CVS, almost entirely) on individual files.
> > > There was no way to link changes that affected more than one
> > > file:
> >
> > That was the problem that BitKeeper solved.  There was an extra step,
> > bk commit, that glued all the files together in an atomic commit.
> > That and each commit was like a CVS tag, you can roll the history back
> > to any commit, no tags are needed.  That's because while you think of a
> > revision as 1.5 or whatever, and BitKeeper had that interface, the real
> > name is a a provably unique key made up of
> >
> >     user@host|path/to/file.c|time_t|sccs_cksum
> >
> > We called those "keys" and you could use a key any place you could use
> > a revision.
> >
> 
> That's a nice feature... Too bad we don't have it for the historic SCCS
> trees.

SCCS doesn't version pathnames so you have to fake it.  You could look at
BitKeeper's import -tSCCS to see what we did, I would think we would have
done something sensible.

> Also, the historical SCCS trees lack metatdata about file renames (which
> were done by moving the ,s files)...

See above.  BitKeeper versioned not only path names (they are an attribute
of each delta) but also file types: symlink, regular, not sure if we ever
did hard links.
-- 
---
Larry McVoy           Retired to fishing          http://www.mcvoy.com/lm/boat

  reply	other threads:[~2024-12-14  0:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13 22:57 Norman Wilson
2024-12-13 23:19 ` Larry McVoy
2024-12-13 23:38   ` Warner Losh
2024-12-14  0:53     ` Larry McVoy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-13 22:33 Norman Wilson
2024-12-17  0:21 ` andrew
2024-12-13 16:52 [TUHS] " Marc Rochkind
     [not found] ` <A6DE3D0A-8ED7-4E82-87CF-F2BC7AE11761@seiden.com>
2024-12-13 17:58   ` [TUHS] " Marc Rochkind
2024-12-13 21:09     ` Dan Cross
2024-12-14  1:11       ` Marc Rochkind
2024-12-14  1:27         ` Dan Cross
2024-12-14  1:39           ` Larry McVoy
2024-12-14  6:20           ` Marc Rochkind
2024-12-14  1:38         ` Larry McVoy
2024-12-13 18:06 ` Larry McVoy
2024-12-13 18:32   ` Marc Rochkind
2024-12-13 18:39     ` Marc Rochkind
2024-12-13 18:49       ` Larry McVoy
2024-12-13 18:55     ` Larry McVoy
2024-12-13 19:55       ` Henry Bent
2024-12-14 18:29         ` arnold
2024-12-14 18:59           ` Larry McVoy
2024-12-13 21:46     ` Clem Cole
2024-12-13 21:22 ` Rob Pike
2024-12-13 21:27   ` Rob Pike
2024-12-13 21:37     ` Aron Insinga
2024-12-13 21:40       ` Aron Insinga
2024-12-14  0:37 ` Luther Johnson

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=20241214005305.GE11590@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=imp@bsdimp.com \
    --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).