[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Annoying CVS 1.11 behavior.
From: |
StyxLord |
Subject: |
Re: Annoying CVS 1.11 behavior. |
Date: |
Sun, 21 Oct 2001 18:52:34 GMT |
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" <address@hidden> wrote in message
news:address@hidden
> 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.