What are semantics of "Node-action: replace"

While struggling with other issues noted on this list (see aside at
end), I started looking at the svn dump format and have a couple of
questions

1) When is node-action "replace" used and what are the implications
thereof? Is it simply used instead of "add" when the indicated path
already exists (presumably via "svn move" or "svn copy")? Or is it ever
used instead of a "change" action? For that matter, would anything go
wrong if "change" were used instead of replace?

2) Is there any documentation on the dump file format with more
extensive discourse that the document "dump-load-format.txt"? Or
alternatively, is there other design documentation that discusses the
details of the various node-actions?

ASIDE - What is motivating this is trying to understand how hard it
would be to hack up a dump file to address some of the problems
encountered in deleting old history, an in:

        svnadmin dump repo -r2000:9999 | svnadmin load virgin-repo

which complains if any of revs 2000-9999 were copied from revs prior to
2000.

Thanks for any insight,
-- Charlie

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-21 01:18:37 CET