Re: Copying a part of another repository, *with* its history

On Tue, May 06, 2008 at 09:04:11AM -0700,
 Kevin Grover <kevin_at_kevingrover.net> wrote
 a message of 158 lines which said:

> The tough points are:
> 1) You may have to edit the dump file to get the paths to be what you want
> in the destination repository

In my case, it was apparently not necessary. If it had been, I would
have used sed to edit "Node-path" lines in the dump.

> 2) You have to be careful about which directories exist and which need to be
> created

That was the trick *and* I needed to commit as well, not just to
create the directories in a working copy as I did once :-(
 
> To prevent accidentally editing the 'old' source, you should 'svn delete'
> the path from the source repository after successfully migrating it.

Right.
 
> Tools: svndumpfilter (comes with CLI svn install), svn_load_dir.pl (and
> there's also a newer re-implementation in python, call svnload.py (I think).

I used only regular "svnadmin load". svn_load_dir.pl seems to be for a
different use.
 
Many thanks for the help, I do some more tests and I'll try with my
real repository soon.

Some warnings: the revision numbers are not preserved (obviously), the
dates are, but, now, in the new repository, the order of revisions is
no longer the chronological order.

I attach a shell script which I used to test the procedure. It
demonstrates the steps to perform.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org