The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Henry Bent <henry.r.bent@gmail.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: Marc Rochkind <mrochkind@gmail.com>,
	The UNIX Historical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: SCCS roach motel
Date: Fri, 13 Dec 2024 14:55:58 -0500	[thread overview]
Message-ID: <CAEdTPBcjW_rXf+g=0twQrU0Dfsj6yytNHA_+N5Byr__4YxKHCQ@mail.gmail.com> (raw)
In-Reply-To: <20241213185534.GY11590@mcvoy.com>

[-- Attachment #1: Type: text/plain, Size: 981 bytes --]

On Fri, 13 Dec 2024 at 14:03, Larry McVoy <lm@mcvoy.com> wrote:

> On Fri, Dec 13, 2024 at 11:32:57AM -0700, Marc Rochkind wrote:
>
> > Was your implementation of SCCS ever released by itself?
>
> See if the wayback machine has BitSCCS somewhere.  It was pretty early,
> before Rick showed up to fix my screwups.  He did point out that my
> weave implementation was the only one written such that I could have
> N serial sets in my hand, and do one pass through the weave and get
> N different checked out files.  I don't think we ever used that but
> if we did it would be in smerge.c.
>

There are many preservations of http://www.bitmover.com/bitsccs/, but since
the BitSCCS sources were distributed via FTP the wayback machine doesn't
have the actual sources.

I did a bit of searching and found
ftp://linux.mathematik.tu-darmstadt.de/pub/linux/distributions/historic/jurix/source/compile/BitSCCS-0.5.2.tar.gz
; I don't know where that falls in the product's lifetime.

-Henry

[-- Attachment #2: Type: text/html, Size: 1556 bytes --]

  reply	other threads:[~2024-12-13 20:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2024-12-13 22:33 Norman Wilson
2024-12-17  0:21 ` andrew
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

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='CAEdTPBcjW_rXf+g=0twQrU0Dfsj6yytNHA_+N5Byr__4YxKHCQ@mail.gmail.com' \
    --to=henry.r.bent@gmail.com \
    --cc=lm@mcvoy.com \
    --cc=mrochkind@gmail.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).