[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 16:58:06 GMT
"Frederic Brehm" <address@hidden> wrote in message
> At 08:04 PM 7/31/2004, sfgaijin wrote:
> >What I would like to do is rebuild a module , which contains a bunch of
> >source files, without losing the revision history.
> How about copying all of the *,v files to the new system?
The question is how to do it such that the *,v files are recognized
correctly by the new system?
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.
Would untarring the file under CVSROOT and editing the modules file work ?
- Re: using cvs history files e, g foo.c, v to clone a hierarchy and retain the history,