Stefan Sperling writes:
> Can you explain what you mean by "resume support"?
> svnadmin dump has no such feature AFAIK.
I like to think of svnrdump as a combination of `svnsync` and
`svnadmin dump`. To illustrate resume support, consider the following
scenario: Suppose a server administrator wants to backup a remote
repository (with a large number of revisions) over a slow unreliable
Here's the current way of doing it (using `svnsync`): run `svnsync
init` first, and then `svnsync sync`. When the connection breaks,
re-run `svnsync sync` and it'll just resume dumping.
Here's my proposed new way of doing it (using `svnrdump`): run
`svnrdump` with a revision argument and redirect the output to a
dumpfile. When the connection breaks, run `svnrdump resume` with the
dumpfile as the argument. To implement resume support, we have to
actually read the dumpfile ofcourse.
> In any case, using svnsync-specific meta-data to implement an
> svnrdump-specific feature sounds wrong.
Received on 2010-07-23 20:13:47 CEST