Hi Andy,
> From: [EMAIL PROTECTED] On Behalf Of Jim.Hyslop
>
> If they will be modifying the code, then your approach will not work. They
> will have to check out the branch tag for the legacy branch. You
> might want
> to write a simple script or batch file that will check out the appropriate
> directories for them, something like:
>
> cvs co project
> cd project
> cvs update -r yourbranch legacy_directory
The difficulty lies because the "yourbranch" tag only exists in the legacy
directory. With "cvs admin" command you can attach the "yourbranch" tag to
the rest of the project and subsequently use it to checkout that branch in
a single operation AND continue developing that branch. To use admin:
cd top_project_directory
cvs admin -n yourbranch:1
expect error messages where "yourbranch" tag already exists. The revision
number ":1" is the absolute value of the "trunk". The admin command is
adding the "yourbranch" tag to files that don't already have it. The tag
value is "1" which is the branch id of the "trunk". Adjust the ":1" to be
either an existing branch tag or branch number in "mixed" branch cases.
To develop:
cvs checkout -r yourbranch
OR
cvs update -dP -r yourbranch
Read the caveats on "cvs admin" command. It's not intended for general
use and you can create quite a mess if used incorrectly:
http://www.cvshome.org/docs/manual/cvs-1.11.14/cvs_16.html#SEC119
Best regards,
Conrad Pino
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
