Path: utzoo!attcan!uunet!husc6!mailrus!ames!killer!vector!rpp386!jfh
From: jfh@rpp386.UUCP (John F. Haugh II)
Newsgroups: comp.unix.questions
Subject: Re: RCS and SCCS
Message-ID: <3494@rpp386.UUCP>
Date: 2 Jul 88 01:04:33 GMT
References: <890@fig.bbn.com> <710@ubu.warwick.UUCP> <661@pyuxe.UUCP> <29953@cca.CCA.COM> <1023@unccvax.UUCP> <8187@brl-smoke.ARPA>
Reply-To: jfh@rpp386.UUCP (The Beach Bum)
Organization: Big "D" Home for Wayward Hackers
Lines: 32

In article <8187@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>In article <1023@unccvax.UUCP> wdg@unccvax.UUCP (Doug Gullett) writes:
>>... a few manual pages
>>would bring programmers up to speed on RCS while whole volumes are written
>>about the use of SCCS.
>
>This is quite misleading.  I haven't seen "volumes" on SCCS, but it is
>easy to use for routine purposes.

i've seen several long SCCS documents, the longest of which was the SCCS
User's Guide, which i recall was about 50 or 75 pages long, which arrived
with System III.  i've seen other disertations on SCCS, tho none that
long.

SCCS seems to be extremely simple for simple tasks.  but the curve for harder
tasks is like O(N**2) or something.  trying to maintain multiple branches
is HELL, and the error messages which can result are cryptic.  which isn't
too bad because the error messages are very standardized with SCCS, and
the help command is actually helpful.

the hardest thing is learning about commands like admin -z for dealing with
corrupted files.  and then there are the quirks of rmdel, cdc, comb (which
i think i must be the only person who uses) and the rest of the members
which doug didn't reference.  there is much more to SCCS than admin, get
and delta.

- john.
-- 
John F. Haugh II                 +--------- Cute Chocolate Quote ---------
HASA, "S" Division               | "USENET should not be confused with
UUCP:   killer!rpp386!jfh        |  something that matters, like CHOCOLATE"
DOMAIN: jfh@rpp386.uucp          |             -- with my apologizes