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: dewar@cs.nyu.edu (Robert Dewar) Subject: Re: Configuration Management for Ada on Unix Date: 1996/06/05 Message-ID: #1/1 X-Deja-AN: 158644841 references: <9605301407.AA03821@most> <31AE05C9.36BE@csehp3.mdc.com> <31AF7F12.6DE9@csehp3.mdc.com> <31B30862.6F03@csehp3.mdc.com> <31B59D77.29D4@csehp3.mdc.com> organization: Courant Institute of Mathematical Sciences newsgroups: comp.lang.ada Date: 1996-06-05T00:00:00+00:00 List-Id: James Squire says "Seriously, using 'branch' as a 'baseline' is exactly the kind of kludge that I said before I am not interested in. I don't want to have millions of different branches. Moreover, what if I also want to use branches what they were designed for, namely variants supporting multiple platform or bug fixes to old versions? Now I've got to come up with an extra naming convention to distinguish traditional branches from those that I am using to represent baselines. Now I've got a mess." I don't understand this at all. I see two different uses of this same fundamental concept. But at the tool level it is silly to have two names for the same thing. You can call a branch anything you want, surely we are not spending this energy arguing just about terminology? especially when we know that no one agrees on this terminology.