Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mcnc!thorin!unc!cheung
From: cheung@unc.cs.unc.edu (Clement Cheung)
Newsgroups: comp.software-eng
Subject: Re: Source Code Control
Message-ID: <8667@thorin.cs.unc.edu>
Date: 28 Jun 89 00:15:13 GMT
References: <791@redsox.bsw.com> <357@umigw.MIAMI.EDU> <1625@zen.co.uk>
Sender: news@thorin.cs.unc.edu
Reply-To: cheung@unc.cs.unc.edu (Clement Cheung)
Organization: University Of North Carolina, Chapel Hill
Lines: 26

In article <1625@zen.co.uk> vic@zen.UUCP (Victor Gavin) writes:
>What's wrong with named versions?
>
>Just "rcs -nVersion_1 RCS/*" (or use rcsfreeze, which checks in your files
>for you as well), and everything has a consistent ``name'', you no longer
>have to keep each file at the same revision code or make unwieldy abuse of
>features designed for other uses.
>
>				vic
>
>Victor Gavin						Zengrange Limited

If you say co -l2.0 sysrc.c , RCS will give sysrc.c of version 2.0 or less 
depending what is the latest version. But if you give a name for version
2.0 of sysrc.c then RCS will only return version 2.0 of sysrc.c if it has it.

But identifying a version by name is not powerful enough because it does
not convey any information about that particular version. A lot of the
research SCM systems identify a version by attributes values. These
attributes describe the properties of that version of the program.
This concept is already in DSEE. A version that matches the specified 
attributes values is selected. In DSEE you can also have preferences
for your selection. You lists the most desirable properties before 
the less desirables properties. 
 
Clement Cheung.