[EMAIL PROTECTED] wrote:
> 
>   A. checkout new working dir using new repository location
>   B. transfer content of old working copy to new working copy
>   C. delete and cvs remove files from new working copy if necessary
>   D. get rid of old working copy and continue work in new working copy

That is pretty fool-proof, but you lose existing intermediate build
files, which may or may not be a big deal.

> Mike Ayers <[EMAIL PROTECTED]>
>
>                  4.  Run a script which deletes all the CVS/Root
> directories and then
> `cvs -d /new/path/to/repository update`

s/directories/files/ and this works. Nice tip! Much better than running
N processes to delete/modify existing files...

Also note that if $CVSROOT is defined to the new location, you can just
'cvs up'. 

-Matt


_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Reply via email to