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,
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
Tested with -P, same results as without.
> - When you do a "cvs log" of a file in B/otherDir
gging only dependant
modules necessary to build an individual app. E.g. project1 depends on
sources in project3 so I apply tags and branchtags like so:
cvs rtag -rALLSRC_01 APPLICATION_1_0_0_3 A/3rdparty A/project1
B/project3
I have 2 questions:
1. Is this tagging method acceptable?
2. If so, whe
B/project3
I have 2 questions:
1. Is this tagging method acceptable?
2. If so, when I check out thusly: cvs co -rAPPLICATION_1_0_0_3 A B,
why do I get some extra directories and sources that where not
explicitly tagged (e.g. B/otherDir)
--Russ
"Everything you see, I owe to spaghetti.&q
