2015-08-22 21:22 GMT-03:00 :
> Can you confirm that the file is locked after the command? (E.g. by
> running svn status on the target)
>
> Does it lock the file when the hook blocks it… or does ‘svn lock’ return
> success?
>
No, it doesn't.
Look at these comnands, using svn 1.9, first without a h
Can you confirm that the file is locked after the command? (E.g. by running svn
status on the target)
Does it lock the file when the hook blocks it… or does ‘svn lock’ return
success?
At the api level the lock command performs a callback per target to return the
failure/success of each target,
Vincent Lefevre writes:
> On 2015-08-20 17:12:58 +0100, Philip Martin wrote:
>>
>> It is recorded the same way all other auth credentials are recorded.
>
> Except for svn+ssh (which is what I always use) because the
> auth credentials are part of the SSH configuration.
In what way is it differe
Hi there,
It seems that svn 1.9 changed the behaviour of the "svn lock" and the "svn
unlock" commands with regards to the fate of the corresponding
pre-lock/pre-unlock hooks.
Up to svn 1.8, when those hooks failed (exit code != 0) the commands (svn
lock/unlock) failed too.
Now, on svn 1.9, the c
