Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!rochester!rit!ultb!dnk8842
From: dnk8842@ultb.UUCP (D.N. Kadoch)
Newsgroups: comp.software-eng
Subject: Re: Source Code Control
Message-ID: <962@ultb.UUCP>
Date: 22 Jun 89 12:50:26 GMT
References: <133@tirnan.UUCP> <8100004@gistdev>
Reply-To: dnk8842@ultb.UUCP (D.N. Kadoch (635EMC))
Organization: Rochester Institute of Technology, Information Systems
Lines: 23

In article <8100004@gistdev> joe@gistdev.UUCP writes:
>I think that this is true in several regards.  When we set up our source code
>control system (we use SCCS, and yes, we looked at RCS), we found (like
>everyone else), that controlling source files is not enough.  You need the
>ability to track the state of a "program"
>including not just source code, by documentation, make files, testing files,
>and any other associated text.

	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.
-- 
/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\
>  Dani Kadoch  @ Computer Science House @ Rochester Institute of Technology  <
>        USNail: 14 Loden Lane, Rochester, NY 14623    (716) 359-4647         <
>   UUCP:..!rochester!rit!ultb!dani    MCIMail:dani   BITNET:dnk8842@ritvax   <