Found that this works for me. Create the branch first and then when commiting the new files you can commit the directly to the branch.
cvs commit -r <branchname> <newly added files> Cheers, Matt. "Kaz Kylheku" <[EMAIL PROTECTED]> wrote in message ObZz7.98922$[EMAIL PROTECTED]">news:ObZz7.98922$[EMAIL PROTECTED]... > Suppose you are hacking away on some code, and as part of the hacking you > ``cvs add'' some files (but do not commit). Then you decide that you want > to commit everything on a new branch, because it is simply too > experimental. You try to do cvs tag -b <branchname>, but the software > complains that it knows nothing about your added files, aborting > the tagging operation! > > The behavior should probably be: just tag everything and leave the added > files alone. Then when the user updates to the newly created branch, > CVS/Entries for the added files should be updated with the new tag so > that the commit of the cvs add will go to the branch. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
