On Thu, 2003-01-30 at 22:18, Simon Scott wrote: > Does anybody know of any issues with this or better way to achieve what I > want?
module A: common components. module B: diverse components. When working on common components, use module A. Consider having a 'floating' tag called 'stable'. When working on diverse components, use module B (either -r legacy or -r future). In your build/test script, checkout A -r stable, and B -r whichever, and compile. I'm also sure there's some way you could use ampersand modules in CVSROOT/modules to get what you're after, but I can't figure it out. It'd start with: A: common B: diverse C: &A &B But I'm not sure how the branching would work. Probably something like cvs checkout -f -r legacy C, where you've developed A without the branch so the -f fetches the head of A. Jenn V. -- "Do you ever wonder if there's a whole section of geek culture you miss out on by being a geek?" - Dancer. My book 'Essential CVS' will be published by O'Reilly in 2003. [EMAIL PROTECTED] http://anthill.echidna.id.au/~jenn/ _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs