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/05 Message-ID: #1/1 X-Deja-AN: 158586982 sender: kingdon@harvey.cyclic.com references: <9605301407.AA03821@most> organization: very little newsgroups: comp.lang.ada Date: 1996-06-05T00:00:00+00:00 List-Id: > It seems to me that the concept would break down, unless of course you > can version control the directory itself. Yes, CVS can version control directories as of version 1.5 (the so-called "death support" features). > But once I establish that the baseline is correct, it becomes frozen. > I need to be able to retrieve it later, plus I need to get on with the > latest version - which will mean changes right there in that same > branch and directory. If that is what you want, then you just need a tag, not a branch. > To me, one of the aspects of a CM product should be that one of the many > objects it operates on is called "baseline" - and this should be a > separate construct apart from branches or labels or whatever. It's > cleaner and safer. If I recall correctly, last time the term "baseline" was discussed on comp.software.config-mgmt, people could not agree on what it meant. So I'm not sure that using that word would decrease confusion rather than increasing it.