Philip Martin <[email protected]> writes: > Daniel Shahaf <[email protected]> writes: >> >> Either method would need to account for old-revprop changes and for 'svn >> lock' locks. > > Unless we start recording some sort of history for revprops the only > option for svnsync is to resend all revprops, hotcopy has more options.
As you know, hotcopy gets locks wrong at present (issue 3750). I've just thought of another thing to add to that issue but tigris.org is down so I'm recording it here: hotcopy currently copies revs then locks. Nothing prevents the source adding a rev and a lock after hotcopy has copied revs and before it copies locks. That means the copy could have a lock on a file that does not exist in the copy. I'm not sure there is any copying order we can use that will avoid the problem, we may need to add a post-copy step to audit the locks. -- Philip
