Hi, you need to not read the svnbook quite so narrowly. :-) The main reason dump/load was written was to be able to migrate history from one DB schema to another (for example, from BDB to FSFS) by creating a dumpfile whose format is a 'neutral' representation of data. We used it a lot in the early days too, back when repository data formats were still in flux. Turns out you can also use it for backing up repositories incrementally, or for editing history and re-slurping it into a new repository.
The main reason svnsync was written was to push history over a network -- something dump and load can't do. svnsync is incredibly simple: it talks to two repositories over the network (possibly using different network protocols, even) and does an "svn update" from one, then turns around and does an "svn commit" to the other. It knows nothing about data formats, it's just a mindless update/commit pipe. It was written mainly to create read-only mirrors of "central" repositories. That's why book discusses mirroring so much: it's pointing out that if you commit to a mirror yourself, then it will no longer be in lock-step with the original repository, and svnsync will refuse to push to it anymore. But there's nothing that *requires* you to make a mirror. In your situation, you'd be using it as a one-time migration. svnsync from server A to server B, then throw away server A and start doing regular development on server B forever after. So both dump/load and svnsync are different ways of migrating history. The former method requires direct shell access to both repositories, the latter only requires network access to both. Since Google isn't in the habit of passing out shell accounts to users, we instruct them to migrate using svnsync. :-) -- an svnbook author --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
