Justin Erenkrantz wrote:
> --On Thursday, October 24, 2002 4:08 AM -0700 Greg Stein
> <gstein@lyra.org> wrote:
>
>> Ideally, cvs2svn could see an add/remove in a commit and determine
>> it was a move. But copies are a bit tougher. But the case that I'm
>> thinking of is the conversion of the Apache web server. At some
>> point, Apache 2.0 was forked out of the 1.3 development tree. If
>> cvs2svn could build an aggregate repository of the 1.3 and 2.0
>> repositories, and also have an 'svn cp' for the point where 2.0 was
>> copied... hoo that would rock. You could trace 2.0 files all the
>> way back in time.
>
>
> Woah, that would rock.
>
> I'll be buying lots of beer for the interested parties if cvs2svn could
> do this. -- justin
This is the reason why I started hacking cvs2svn. I have the same
situation for my window manager (3 modules, the latter two starting as
branches of the previous one).
This could be done semi-automatically by converting one module at the
time and manually preparing the correct repository state in-between
(/trunk would need to be the same as the initial import of the next module).
MArk
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 25 06:47:47 2002