I'm quite new to using CVS.
Our applications rely on common source, and built products alike.
Some of these are 3rd party (dlls, jars, source, etc.) and some are internally
developed.
For instance, to build release 1.2 of product X, I need release 3.4 of product A,
release 5.4 of product B,
At 10:15 AM 9/26/2002, Jay Yarbrough wrote:
To build release 2.1 of Product Y, I will use release 3.4 of product A,
release 5.3 of product B, and release 2.0 of product D.
How is this typically handled within CVS?
Make each product a separate module. Then you can tag each release of each
Jay Yarbrough wrote:
I'm quite new to using CVS.
Our applications rely on common source, and built products alike.
Some of these are 3rd party (dlls, jars, source, etc.) and some are internally
developed.
For instance, to build release 1.2 of product X, I need release 3.4 of product
Jay Yarbrough wrote:
I'm quite new to using CVS.
Our applications rely on common source, and built products alike.
Some of these are 3rd party (dlls, jars, source, etc.) and some are internally
developed.
For instance, to build release 1.2 of product X, I need release 3.4 of product A,
