Path: utzoo!attcan!uunet!husc6!ukma!nrl-cmf!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.questions
Subject: Re: RCS and SCCS
Message-ID: <8210@brl-smoke.ARPA>
Date: 2 Jul 88 19:00:59 GMT
References: <890@fig.bbn.com> <710@ubu.warwick.UUCP> <661@pyuxe.UUCP> <29953@cca.CCA.COM> <1023@unccvax.UUCP> <8187@brl-smoke.ARPA> <3494@rpp386.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <3494@rpp386.UUCP> jfh@rpp386.UUCP (The Beach Bum) writes:
>there is much more to SCCS than admin, get and delta.

My point is that you rarely need to worry about the others.

We use SCCS routinely here (some of us do, anyway), and I recall
using "comb" and "prs" only a couple of times each, "sccsdiff" a
few times, and other SCCS utilities I didn't mention not at all.
We have used some of the "admin" options to control who gets to
modify the archives etc. but even that is wrapped up in a "new_sccs"
shell script so it's easy to use.

I agree that SCCS is not perfect (branch deltas are a botch, for
example), but neither is RCS.