Hi Philip,
It is a conflict. Values didn’t change after applying the patch.
root@contrail-ubm-dipuh:/tmp/tests# svn patch /tmp/patch
C xpathleak.py
> rejected hunk ## -0,0 +1,1 ## (svn:executable)
Summary of conflicts:
Property conflicts: 1
root@contrail-ubm-dipuh:/tmp/tests# svn diff xpathleak.py
root@contrail-ubm-dipuh:/tmp/tests#
Thanks,
Dipu H
On 6/28/18, 8:49 PM, "Philip Martin" <phi...@codematters.co.uk> wrote:
Daniel Shahaf <d...@daniel.shahaf.name> writes:
> You mentioned earlier that svn:executable was present with an empty
> value. Is that really the case? If it is --- which would be surprising,
> as it's supposed to be an impossible state --- it would explain why you
> got a conflict.
The normalization of svn:executable values is implemented in the client.
If some client chooses not to implement that normalization the backend
will store any value given.
Should the svn client silently merge '' and '*' for svn:executable
values or should it be a conflict? I favour the conflict but I can see
arguments for a silent merge.
--
Philip
