Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/3/85; site ukma.UUCP
Path: utzoo!watmath!clyde!cbosgd!ukma!david
From: david@ukma.UUCP (David Herron, NPR Lover)
Newsgroups: net.unix-wizards
Subject: Re: Sccs vs. Rcs
Message-ID: <1767@ukma.UUCP>
Date: Thu, 16-May-85 20:02:14 EDT
Article-I.D.: ukma.1767
Posted: Thu May 16 20:02:14 1985
Date-Received: Sat, 18-May-85 00:43:26 EDT
References: <1742@ukma.UUCP> <5688@umcp-cs.UUCP> <832@genrad.UUCP> <5715@umcp-cs.UUCP>
Organization: U of Kentucky, Mathematical Sciences, Lexington KY
Lines: 22

In article <5715@umcp-cs.UUCP>, chris@umcp-cs.UUCP (Chris Torek) writes:
> However, co -p should do what the original poster was asking about, right?

Not quite.  In my original posting I was complaining that it's nontrivial
to learn how to use rcs.  Therefore you want to keep the source file out
where it's easy to look at it.  (We're talking here about graduate students
who aren't system administrators ... not the type of people who would
already know what rcs is).  But if you also want to use rcs (or even 
sccs) to keep track of versions, you have an extra copy on disk plus diff's
between versions.  High cost making the sources available.  More than doubling
the disk space used, not to mention backup tapes, etc.


-- 
--- David Herron
--- ARPA-> ukma!david@ANL-MCS.ARPA or ukma!david<@ANL-MCS> 
---	   or david%ukma.uucp@anl-mcs.arpa
---        Or even anlams!ukma!david@ucbvax.arpa
--- UUCP-> {ucbvax,unmvax,boulder,oddjob}!anlams!ukma!david
---        {ihnp4,decvax,ucbvax}!cbosgd!ukma!david

	"It's *Super*User* to the rescue!"