Royce <[EMAIL PROTECTED]> wrote: > (from top directory within tree) > cvs tag v2_0_unstable_root > cvs tag -b -r v2_0_unstable_root v2_0_unstable
followed by cvs update -r v2_0_unstable > I have not checked in the files because I wanted to be sure they will > check into the branch. How can I verify the code will check into the > branch? I'd do a 'cvs status | less' and make sure every file has the sticky tag. Maybe also 'cvs -nt commit' (-n to block the actual commit, -t for a trace of what would happen), but I'm not sure that will show you what revision numbers would be used by a real commit. > cvs log doesn't seem to show that info. I read somewhere that > the branch gets created on commit - is that true? Yes, if you really commit to the new branch. -- pa at panix dot com _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs