RJLRef: $PH/COOL-BDE/BdeCheckoutBranchTags050509r1.txt Oops here's another typo: Creating a branch tag is done by cvs [r]tag -b BdeSELogBranch bde and option -b is not available at checkout. To check out the branch tagged BdeSELogBranch, use cvs co -r BdeSELogBranch bde. (not cvs co -b BdeSELogBranch bde as I said below). Forwarded message: > From lechner@cs.uml.edu Mon May 9 14:47:02 2005 > From: Bob Lechner > Message-Id: <200505091847.j49Il0BA494545@saturn.cs.uml.edu> > Subject: Re: ??? - No, 'with' does NOT help: see stdout below part of the command! ? > To: normgross@yahoo.com (Norm Gross), harshjha82@yahoo.com, hjha@cs.uml.edu > Date: Mon, 9 May 2005 14:47:00 -0400 (EDT) > Cc: 05s523 > RJLRef: $PH/COOL-BDE/BdeCheckoutBranchTags050509.txt > > This CVS experience illustrates the fact that man's > best intentions 'gang aft aglay' (go oft astray :-). > > (Also that software believes your intentions are > accurate, acccording to ITS syntax and semantics, > which are often not human, for experts and novices). > > > From normgross@yahoo.com Mon May 9 10:18:44 2005 > > From: Norm Gross > > Subject: Re: ??? - No, 'with' is NOT part of the command! ???????? > > To: Bob Lechner > > > > It must have been a fluke that it worked when I > > literally typed 'with' because it did a checkout (I > > tried it both ways). Neither the the 'man cvs' nor > > the error message had any mention of a -b option. > > > > > [ngross@mercury finalproj]$ cvs co -b BdeSELog bde . > > > co: invalid option -- b > > > > --- Bob Lechner wrote: > > > ??? - No, 'with' is NOT part of the command! > > > ???????? > > > > Norm, you are too trusting - :-) CVS is a good product > but it is blind like all SW to your real intentions- > It blindly follows its own interpretation of commands. :-) > Here is what happened when I tried the same thing just now: > ----------------- > > I did mkdir NGTestCVSco-b and in there did > 'cvs co with -b BdeSELog bde' > I was shocked to see that 'with' actually appeared to work. > However, CVS' real behavior is revealed by its feedback > at the START of the cvs co process, before the many pages > of per-file checkout reports: > > ------------------ > mercury.cs.uml.edu(9)> pwd > /nfs/earth/faculty/fac1/lechner/NGTestCVSco-b > mercury.cs.uml.edu(10)> ls > mercury.cs.uml.edu(11)> cvs co with -b BdeSELog bde > cvs checkout: cannot find module `with' - ignored > cvs checkout: cannot find module `-b' - ignored > cvs checkout: cannot find module `BdeSELog' - ignored > cvs checkout: Updating bde > U bde/Imakefile > ...etc... > ---------------- > [You have to save a typescript or adjust window buffer > length to a few hundred lines and scroll back to see it. > (An option not in putty Settings - I can't find it:-( > CVS option -q (quiet) might help but CVS might then > throw out the baby with the bath-water.] > > > So cvs failed to check out what it THOUGHT > you asked for (three modules: 'with' '-b' 'BdeSELog'), > before it checked out the bdei tree. Now bde has > NO bde/CVS/Tag file, because CVS thought you > wanted to check out on the trunk, not as a branch. > (Allowing '-' as first char of a filename is a little > risky on CVS' part: It means if you check in any > changes you corrupt the trunk version which your > project should not touch while SB/LM/MM are testing > bde with genv13 there. > > So ALWAYS make sure CVS/Tag exists and contains > the branch (T) tag BEFORE you check back in > (or even update) local files. CVS maintains that > file - you should NOT change it yourself, > even though it is local to every bde tree directory. > > Incidentally, tag BdeSELog no longer exists - > I deleted it and retagged it as BdeSELogBranch > because that's what I asked for in line with the > Fogel CVS text's advice. If yuou check out > this branch (cvs co -b BdeSELogBranch bde) > you should get (the latest revs on) this branch > and bde/CVS/Tag will contain "TBdeSELogBranch". > Otherwise, try again. > > Actually I think you will check out the tip > of this branch - not its initial version. > I actually added a comment to bde/configure.h > which might upgrade its tagged revision# by one. > > So it's important for all teams to inspect CVS/Tag > existence and content to know what they are > updating in the CVS database. > > (Welcome to the world of version control > and configuration management:-) > > R Lechner. >