Interesting. Just before invoking "cvs tag", can you confirm that B/otherdir is not in your workspace? Does the output of "cvs tag" give any indication of what it's doing at the time it applies the tag to B/otherdir?
>--- Forwarded mail from [EMAIL PROTECTED] >On Wed, 9 Feb 2005 11:23:52 -0800, Paul Sander <[EMAIL PROTECTED]> >wrote: >> Some follow-up questions: >> >> - When you do the checkout, do you use the -f or -P options? >Niether. I do a clean cvs co -rTAG <base module> >Tested with -P, same results as without. >> - When you do a "cvs log" of a file in B/otherDir, is the tag listed? >The tag is in fact listed for all files in the extra directory. >This seems to point towards me having inadvertantly tagged that >directory. So I did another test: >rm -rf A B >cvs co -rOTHER_TAG A/3rdparty A/project1 B/project3 >cvs tag NEW_TAG A B >rm -rf A B >cvs co -rNEW_TAG A B >Once again, B/otherdir is there and the log shows it tagged as >NEW_TAG... >--- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs