From: William Corcoran <wlc@jctaylor.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] SCCS
Date: Thu, 12 Sep 2019 06:12:10 +0000 [thread overview]
Message-ID: <03956472-B6A1-4E83-B2F1-0FE855C75C15@jctaylor.com> (raw)
In-Reply-To: <20190912043308.GL2046@mcvoy.com>
Okay, while on the subject of SCCS and UNIX:
Is there a UNIX (post SCCS) like System III or System V that still has all of the original SCCS entries intact?
Would only production ready code be entered as an SCCS delta?
Or, would SCCS be used as a checkpoint tool to store unofficial versions (even broken versions) of the UNIX codebase as development progressed on the system as a whole?
I would love to see all of the prs for the kernel and commands.
Truly,
Bill Corcoran
> On Sep 12, 2019, at 12:33 AM, Larry McVoy <lm@mcvoy.com> wrote:
>
> Yeah, this was one of things that BitKeeper addressed. It was easier
> to use and every commit was a tag.
>
>> On Wed, Sep 11, 2019 at 09:28:25PM -0700, Jon Forrest wrote:
>>
>>
>> I used both RCS and SCCS in the early days (e.g. 1985 - 1991). RCS was
>> what we used at Britton-Lee in the group that Eric Allman was part of.
>> SCCS is what we used at Sybase as it was gaining popularity. This was
>> so long ago that I don't remember all the details but I found that
>> RCS was much easier to use, especially in an environment that didn't
>> do much merging. Instead we used labels (or tags, I forget what they
>> were called) to mark which files were part of which release. Doing
>> this was much harder in SCCS, which contributed to the mess that
>> was Sybase software engineering.
>>
>> Of course, all this could be explained by Eric's deep knowledge
>> of RCS, and the lack of somebody with Eric's knowledge at Sybase.
>> But, to me, an early adopter of source code control who wasn't
>> overly interested in speed, RCS was much easier to use.
>>
>> Jon
>
> --
> ---
> Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2019-09-12 6:26 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 6:25 [TUHS] PWB vs Unix/TS Warner Losh
2019-09-09 6:36 ` arnold
2019-09-10 15:16 ` Clem Cole
2019-09-11 0:28 ` Steve Johnson
2019-09-11 3:53 ` Warner Losh
2019-09-11 15:36 ` Clem Cole
2019-09-11 16:55 ` [TUHS] IBM Unix source licenses [was " Charles H Sauer
2019-09-12 19:31 ` Kevin Bowling
2019-09-12 20:59 ` Clem Cole
2019-09-12 21:09 ` [TUHS] IBM Unix source licenses - Series/1 NUXI Ronald Natalie
2019-09-12 21:31 ` [TUHS] IBM Unix source licenses [was Re: PWB vs Unix/TS Warner Losh
2019-09-12 22:30 ` jcs
2019-09-12 23:12 ` reed
2019-09-12 23:22 ` jcs
2019-09-12 23:29 ` [TUHS] IBM Unix source licenses Warren Toomey
2019-09-13 7:06 ` arnold
2019-09-13 8:30 ` SPC
2019-09-14 18:29 ` Warner Losh
2019-09-12 21:29 ` [TUHS] IBM Unix source licenses [was Re: PWB vs Unix/TS Charles H Sauer
2019-09-11 17:49 ` [TUHS] " Richard Salz
2019-09-11 17:52 ` ron
2019-09-11 21:44 ` Clem Cole
2019-09-11 18:11 ` Larry McVoy
2019-09-11 18:18 ` Richard Salz
2019-09-11 18:54 ` Larry McVoy
2019-09-11 21:05 ` Steve Johnson
2019-09-11 21:34 ` Steve Johnson
2019-09-11 21:57 ` Clem Cole
2019-09-11 22:50 ` Arthur Krewat
2019-09-11 21:59 ` Clem Cole
2019-09-11 21:50 ` Clem Cole
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:31 ` [TUHS] [SPAM] SCCS Larry McVoy
2019-09-12 13:44 ` Tony Finch
2019-09-13 4:11 ` Larry McVoy
2019-09-13 5:54 ` Dave Horsfall
2019-09-13 8:00 ` Peter Jeremy
2019-09-13 15:23 ` Larry McVoy
2019-09-13 21:36 ` Dave Horsfall
2019-09-12 4:28 ` [TUHS] SCCS Jon Forrest
2019-09-12 4:33 ` Larry McVoy
2019-09-12 6:12 ` William Corcoran [this message]
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
2019-09-11 16:05 ` [TUHS] PWB vs Unix/TS Paul Winalski
2019-09-11 17:14 ` ron
2019-09-14 0:44 ` [TUHS] a book (was Re: PWB vs Unix/TS) reed
2019-09-14 2:53 ` Warner Losh
2019-09-15 2:18 ` Jon Steinhart
2019-09-15 2:39 ` Clem Cole
2019-09-15 3:24 ` Adam Thornton
2019-09-14 22:46 ` Clem cole
2019-09-15 0:58 ` Adam Thornton
2019-09-15 3:30 ` Eric Allman
2019-09-15 4:21 ` Larry McVoy
2019-09-15 5:17 ` Jon Steinhart
2019-09-15 20:14 ` Clem Cole
2019-09-15 20:21 ` Jon Steinhart
2019-09-15 20:12 ` Clem Cole
2019-09-15 21:28 ` Dave Horsfall
2019-09-15 23:27 ` Clem cole
2019-09-15 23:45 ` Richard Salz
2019-09-15 7:43 ` Andy Kosela
2019-09-12 4:25 [TUHS] SCCS Jon Steinhart
2019-09-13 21:37 Norman Wilson
2019-09-13 21:51 ` 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=03956472-B6A1-4E83-B2F1-0FE855C75C15@jctaylor.com \
--to=wlc@jctaylor.com \
--cc=lm@mcvoy.com \
--cc=tuhs@minnie.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).