On Thu, Aug 4, 2011 at 10:10 AM, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > Nico Kadel-Garcia wrote on Thu, Aug 04, 2011 at 09:53:03 -0400: >> On Thu, Aug 4, 2011 at 9:30 AM, Peter Pommelich <petep...@web.de> wrote: >> > Thanks a lot for that hint! Do you know if it's possible to sync multiple >> > folders of the source repository to the same destination repository? >> > Something like this: >> > >> > svnsync initialize svn://a.repo.org/projA svn://b.repo.org/dest >> > svnsync initialize svn://a.repo.org/projB svn://b.repo.org/dest >> > svnsync initialize svn://a.repo.org/projC svn://b.repo.org/dest >> > ... >> > svnsync sychronize svn://b.repo.org/dest >> > >> > The goal is migrate multiple projects from the source repository to one >> > destination repository. >> > >> > Kind regards, >> > pete >> >> No. svnsync initialize needs to be done on a local filesystem, in any > > Wrong.
??? Ahh, you've a point. It's the part in svnsync documentation about how svnsync init "must point to the root of a repository which has been configured to allow revision property changes". That typically requires access to the repository configuration in the first place, to set up the "pre-revprop-change" hook, and I personally wouldn't allow that kind of remote manipulation of an svnsync repository except from the local filesystem and the owner of the subversion repository. But that's a mtter of taste and security practices, not one inherent in the svnsync command itself, as you correctly point out. >> case, and cannot be executed inside of an existing remote repository. > > Right*. In 1.7 there is a switch that allows you to use an existing > repository (local or otherwise), if you've synced the start of the > repository by other means. I was noticing that. I like it: it could make mirroring, and keeping a mirror updated, much easier.
