Re: Mass moving files onto branch

[Derek R. Price]

Stephen Rasku wrote:

> We aren't replacing the whole product, just part of it.  Our previous
> release, call it A, includes a bunch of HTML and C-based CGI scripts.
>
> The current release, call it B, does all this with PHP scripts.
> Release B is taking longer than we expected (go figure) so we want to
> back-migrate some Release B functionality into Release A.

That makes more sense.

Anyway, if you want CVS to handle the 'cvs rm', 'cvs add' step for you,
you  can do a merge from the trunk to the branch.  Assuming you tagged
the base of your production branch like the CVS manual recommends, the
command should be something like:

    cvs up -rPRODBRANCH_1_0 -jRELEASE_1_0 -j HEAD

Just do it in whatever subdir contains the subsection(s) you wanted.  If
the files you are updating are scattered, it may be easier to use 'cvs
rm' and 'cvs add'.

Derek

--
Derek Price                      CVS Solutions Architect ( http://CVSHome.org )
mailto:address@hidden     OpenAvenue ( http://OpenAvenue.com )
--
It'll take a miracle to get you out of Casablanca and the Germans have outlawed
miracles.

                - Sydney Greenstreet as Senor Ferrari, _Casablanca_