Re: repo manipulation

[Marko Käning]

Hi Todd,

In my description I used paths which would be used with -d option on 
checkout.

> environment, and the directories/files listed in that file exist in both
> repositories, then it should work, though IIRC you should not do it that
> way... the files in that directory are CVS controlled.
I know that I should not... :)

> Try:
> export CVSROOT=/repos/new/
> cvs checkout CVSROOT
> cd CVSROOT
> cp /repos/old/CVSROOT/module .
> cvs commit
Well, of course I wanted to keep the HISTORY! ;)

> {I am almost betting you are going to send another message indicating you were
> talking more about $CVSROOT/MyVersionControlledDataDirectory instead of the
> $CVSROOT/CVSROOT/module module name control file, but I am going to make you
> send it, i.e., if you meant something other than $CVSROOT/CVSROOT/module you
> should have not have abstracted as much.}
Well, I meant of course the $CVSROOT/MyVersionControlledDataDirectory. The 
module named module was a bad choice for this example, I see... Well, and 
here it is, my other message you made me send... ;)

> did your convert work BEFORE you did the copy?
> Have you asked the mercurial convert program author for help?
Not yet, at first wanted to make sure that I am not messing up my CVS repo 
by doing so, before I contact the convert author.

> {Todd is still wishing that they had named the $CVSROOT/CVSROOT/ directory
> something a little less confusing like: $CVSROOT/CVSCONTROL/ }
Hahaha. Right you are!

Marko