-----Original Message----- From: Ramkumar Ramachandra [mailto:artag...@gmail.com] Sent: 27 September 2010 19:58 To: Neels J Hofmeyr Cc: dev@subversion.apache.org; Daniel Shahaf; Stefan Sperling Subject: Re: place of svnrdump
Neels J Hofmeyr writes: > While we're at it... svnsync's slowness is particularly painful when > doing 'svnsync copy-revprops'. With revprop changes enabled, any > revprops may be changed at any time. So to maintain an up-to-date > mirror, one would like to copy *all* revprops at the very least once > per day. With a repos of average corporate size, though, that can take > the whole night and soon longer than the developers need to go home > and come back to work next morning (to find the mirror lagging). So > one could copy only the youngest 1000 revprops each night and do a > complete run every weekend. Or script a revprop-change hook that > propagates revprop change signals to mirrors. :( Of course, you could put a post-revprop-change hook in place to note which revprop was changed, and then run a script that only syncs those revprops. I wouldn't recommend putting the 'sync copy-revprops' command in the post-revprop-change hook, if someone commits a revision then immediately updates the revprop the sync will fail (as the rev may not have been synced yet). If anything, changing svnsync to ignore a failed copy-revprop command if no revision existed to sync to would fix this problem, and the copy-revprop could then be put in the hook without worry.
