Some follow-up questions:
- When you do the checkout, do you use the -f or -P options? - When you do a "cvs log" of a file in B/otherDir, is the tag listed?
On Feb 9, 2005, at 10:36 AM, [EMAIL PROTECTED] wrote:
--Let's try this again....
Greetings,
I am currently maintaining some code in a 2 monolithic cvs repositories.
A/3rdparty A/project1 A/project2
B/project3 B/project4 B/otherDir
When I started working with these repositories the only builds (asside from developer's private builds) where done by tagging building all sources. As these projects diverge, I have been tagging 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, 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)
Paul Sander | "Lets stick to the new mistakes and get rid of the old
[EMAIL PROTECTED] | ones" -- William Brown
_______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
