Loading dump files into existing repository

http://subversion.tigris.org/issues/show_bug.cgi?id=2742




User cmpilato changed the following:

                What    ld value 
               |New value
============================================================
====================
                  Status|RESOLVED                 
|REOPENED
------------------------------------------------------------
--------------------
              Resolution|INVALID                   |
------------------------------------------------------------
--------------------




------- Additional comments from cmpilatotigris.org Fri Mar 16 08:35:23 -0700 2007 -------
Ben, while the --parent-path option is one way to workaround
this guy's
concerns, it's not what he's asking for.

'svnadmin load --parent-path blah' will create paths in his
repository like
/blah/trunk, /blah/branches, ....   That works great for
avoiding the namespace
clashes he's seeing, but changes the path locations in the
target repository
from where they were in the source dumpfile.

All this user wants is for 'svnadmin load' to optionally not
complain about
pre-existing directories that the dumpfile is trying to
create.  In other words,
a way to "blend" overlapping path spaces when you
know that doing so won't cause
any harm.

It's not such a bad idea for power users, though it could
royally confuse those
that don't fully grasp the concept and its dependencies.

Of course, the naive implementation is no good here.  You
have to watch for
loaded revisions that end up not resulting in a new
repository revision at all
(because they consist wholly of adds of already-existing
directories).

REOPENing for evaluation of the actual request.

------------------------------------------------------------
---------
To unsubscribe, e-mail: issues-unsubscribesubversion.tigris.org
For additional commands, e-mail: issues-helpsubversion.tigris.org