From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,3c8a1ddc13ecb354
X-Google-Attributes: gid103376,public
From: kingdon@harvey.cyclic.com (Jim Kingdon)
Subject: Re: Configuration Management for Ada on Unix
Date: 1996/06/02
Message-ID: <m2u3wudpi3.fsf@harvey.cyclic.com>#1/1
X-Deja-AN: 158079324
sender: kingdon@harvey.cyclic.com
references: <9605301407.AA03821@most> <qw6u3wytapf.fsf@gargantua.enst.fr>
organization: very little
newsgroups: comp.lang.ada
Date: 1996-06-02T00:00:00+00:00
List-Id: <comp.lang.ada>


> My point is that there was no explicit mechanism for saying, "stick
> <this> version I just checked in in <that> baseline."

In CVS, one way to do this would be with branches.  One branch would
be the baseline, and non-baseline changes would happen on other
branches.  It is a *big* step up from RCS or SCCS in this respect,
because of its ability to operate on an entire directory tree in one
operation.

> I just wanted to tweak everybody on their sloppy terminology.  I'll go
> away now ;-)

Unfortunately, there is no standard terminology.  From "Spectrum of
Functionality in Configuration Management Systems", CMU/SEI-90-TR-11,
http://www.sei.cmu.edu/~case/scm/tech_rep/TR11_90/1.4_TermClarification.html:

    As to what constitutes a CM system, there is no agreement. . . . But
    it should be noted that existing CM systems provide their own
    combination of functionality rather than a standard set.