>>>>> Daniel Shahaf <d...@daniel.shahaf.name>: > Steinar Bang wrote on Sat, May 21, 2011 at 18:26:30 +0200:
[snip! svnsync and svnrdump] >> .., it would have been nice if it was possible to tell these tools to >> make a clone of a particular part of the repository into a new >> repository (or a dumpfile for that matter). > You should be able to use either of them if you install authz on your > repository such that *any* paths touched in r683 are unreadable by the > user svnsync/svnrdump connect as. I tried adding this to /svn/conf/authz: [/trunk/someprog] * = (everything else in the file are comments) But both tools still break at revision 683, which is in the path /trunk/someprog/metamodeller. svnsync breaks with: ... Committed revision 681. Copied properties for revision 681. Transmitting file data . Committed revision 682. Copied properties for revision 682. Transmitting file data ....svnsync: Error while replaying commit svnrdump breaks with: ... * Dumped revision 680. * Dumped revision 681. * Dumped revision 682. svnrdump: E210008: Error while replaying commit I was using the svn+ssh method to access the repo. Do I need http access to get the effect you were suggesting? The box at the bottom of this web page would seem to indicate that I need the http method: http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html >From that box: "As the server generates the large response, there's no way it can resend an authentication challenge when it reaches the special subdirectory; thus the subdirectory is skipped altogether"
