Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!umd5!ncifcrf!nlm-mcs!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.questions
Subject: Re: RCS and SCCS
Message-ID: <8187@brl-smoke.ARPA>
Date: 29 Jun 88 17:18:48 GMT
References: <890@fig.bbn.com> <710@ubu.warwick.UUCP> <661@pyuxe.UUCP> <29953@cca.CCA.COM> <1023@unccvax.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) )
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 18

In article <1023@unccvax.UUCP> wdg@unccvax.UUCP (Doug Gullett) writes:
>The learning curve for using RCS effectively is probably easier that SCCS.

For routine simple use, that is true, although the difference is not very
significant.  People who know how to write shell scripts can mimic RCS
commands using SCCS utilities, or do even more useful things.

>... 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.

	admin -iFILE s.FILE	# create archive
	get s.FILE		# check out latest version for use
	get -e s.FILE		# check out for editing
	delta s.FILE		# check edited version back in