>>>>> "AB" == Arthur Barrett <[email protected]> writes:
AB> Jake, >> > Don't you just want to move the old branch to the new HEAD? >> > cvs tag -F -b MY_NEW_BRANCH >> >> Actually, I just want to pretend as if I never cut the branch in the >> first place. We AB> . AB> . AB> . >> What I'd like to do is totally blow away PROJECTX as if it never >> existed. Then I would like to cut a new PROJECTX from HEAD so >> that the project will be based on the latest code from HEAD. AB> Yes - that is 'move the old branch to the new HEAD'. AB> Deleting a branch requires use of the 'cvs admin' commands, and AB> as a general rule of thumb if you ever have cause to type 'cvs AB> admin' then it's probably time to go home and come back with a AB> better idea. In 15 years of administering CVS and CVSNT AB> repositories I've never had to use 'cvs admin'. AB> Now moving branch tags is not something to be done lightly, but AB> since you already know that you've nto used PROJECTX branch then AB> it should be OK (of course having backups of your repository is AB> always a requirement for any administrative command). AB> So from within a sandbox with HEAD checked out: AB> cvs tag -F -b PROJECTX AB> What this command does is literally move the PROJEXTX branch to AB> the HEAD revisions, or to put it another way: when you created AB> the PROJEXTX branch it used the latest revision numbers of each AB> file, you now want it to do the same thing again - any files that AB> have 'newer' revisions you want to move the branch to begin at AB> the newer revision. So after I do this command, I would then go to any existing PROJECTX sandboxes and do a 'cvs update' command? I use the HEAD sandbox to move the branch tag but then refresh any existing PROJECTX sandboxes so that it gets the correct revisions? -- Jake Colman Director of Software Development Principia Partners LLC 101 West Elm Street Suite 620 Conshohocken, PA 19428 +1 (610) 755-9786 www.principiapartners.com
