Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!uxc.cso.uiuc.edu!uxc.cso.uiuc.edu!m.cs.uiuc.edu!render
From: render@m.cs.uiuc.edu
Newsgroups: comp.software-eng
Subject: Re: Source Code Control
Message-ID: <39400030@m.cs.uiuc.edu>
Date: 23 Jun 89 19:02:00 GMT
References: <133@tirnan.UUCP>
Lines: 20
Nf-ID: #R:tirnan.UUCP:133:m.cs.uiuc.edu:39400030:000:944
Nf-From: m.cs.uiuc.edu!render    Jun 23 14:02:00 1989


Written  7:50 am  Jun 22, 1989 by dnk8842@ultb.UUCP:
>	I use RCS and ran into the same problem.  My quick solution
>was to use forced updates, meaning every time I wanted to check
>something in, EVERY source/doc was checked in even if some had not
>changed.  That way, I can just check out a specific revision and get
>the entire working source quickly.  This method is probably not too
>good when several people are working on a project, or at least when
>more than one person is editing a source file at the same time.  I
>also had ALL the files checked out whenever working on the program,
>which is not very common practice.  But for a single person working on
>a program, it is adequate.

There is a set of PD shell scripts called CVS which supports use of RCS
by a team of programmers.  It's available from the comp.sources.unix
repository on uunet.uu.net using anonymous ftp.  I don't know how good
it is.

Hal Render
render@cs.uiuc.edu