On Aug 2, 2010, at 05:16, Istace Emmanuel wrote: > Ok, but that's not what i we at work. The local svn will be a "working copy" > of the external svn. In fact, no user have to use the external svn if > there's a local svn. The goal of this is the limit the access to the WAN. If > the external svn is sync twice per day, we can limit these access and > decrease the commit time for internal user (we have no external user). A LAN > commit is faster than a WAN commit (the bandwith is lower for wan) And we > can have a better security, we have no control on what's do on the WAN with > our data and many commit from LAN to WAN are "point of access to private > data" (SSL or not, ssl is not a good security, you can spoof him easily). We > can limit this risk by limitting the data who are sent.
Ok, then I don't think svnsync will help. That's not how it works (and I don't know of anything that does work that way for Subversion, but I haven't done an exhaustive search).
