|Any detailed SCCS documentation? Veenstra@fel.tno.nl (1995-01-29)|
|Re: Any detailed SCCS documentation? firstname.lastname@example.org (Don Bolinger) (1995-02-03)|
|Re: Any detailed SCCS documentation? email@example.com.OZ.AU (1995-02-07)|
|From:||firstname.lastname@example.org.OZ.AU (Thomas Charles CONWAY)|
|Organization:||Computer Science, University of Melbourne, Australia|
|Date:||Tue, 7 Feb 1995 00:50:11 GMT|
>> [Many people prefer RCS, which is available at no charge with no source, to
>> SCCS. They're both quite useful, albeit a little long in the tooth. -John]
My own preference is for CVS which is a layer on top of RCS. RCS is useful
for one person to keep control of revisions, but in a more-than-one-person
environment, managing the locks can become quite painful. With CVS files
do not need to be locked to edit them.
Here at Melbourne Uni, we have been using CVS to manage the development of
a new compiler (release RSN) which currently stands at about 56KLOC. We have
had up to six people working on it at various times, and with CVS we have
experienced very little difficulty and very little bother in managing the
source. I consider CVS to be an *essential* component of any software
CVS is freely available at a gnu site near you.
Return to the
Search the comp.compilers archives again.