[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: using cvs history files e, g foo.c, v to clone a hierarchy and retai
Re: using cvs history files e, g foo.c, v to clone a hierarchy and retain the history
Mon, 02 Aug 2004 14:20:12 -0400
At 12:58 PM 8/2/2004, sfgaijin wrote:
I tried just adding the *,v files into cvs via cvs add and cvs update; but
it did not recognize that the special nature of the files;
i.e. I ended up having a bunch of *,v,v files.
No, no. Just copy the *,v files directly into the new repository.
For example, suppose you want to make a copy of MODULE/FILE from
/OldCVSROOT into /NewCVSROOT. Just
cp -r /OldCVSROOT/MODULE/FILE,v /NewCVSROOT/MODULE
Of course, if the old and new roots are on different systems and you cannot
just copy, then you can use any other mechanism to transport the file from
one system to another.
If you checkout both MODULE sandboxes and run "cvs status FILE" in both,
then the output from both will be identical except for the CVSROOT
Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/