Annoying CVS 1.11 behavior.

[Kaz Kylheku]

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.