On Wed, Feb 18, 2004 at 07:55:20AM -0500, John Peacock wrote:
> Alexey Kharchenko wrote:
> >The idea is that I'm working on CVS to SVN migration and the plan is to
> >switch on per-module basis. It means for the moment I'll be converting
> >2nd+ CVS module to SVN I'll have a running production SVN repository.
> >The question is if there is an easy way to integrate a result of
> >convertion script into the existing SVN repository.
>
> As long as the modules are completely independent of each other, you can
> use cvs2svn on each module sequentially:
>
> cvs2svn.py --dumpfile=module1 --dump-only /path/to/cvs/module1
>
> and then load them into the subversion repository where you want them to be
> using
>
> svnadmin load --parent-dir < module1
>
> I've been testing this and it looks like what I will be doing...
>
This strategy worries me because svn assumes that revisions occur at
monotonically increasing times.
If you try to specify revisions by date, I'll bet you get unexpected
results.
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 18 14:22:40 2004