Philip Martin wrote on Thu, Jun 28, 2018 at 16:19:30 +0100: > 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.
Thinking out loud: Since the normalization happens in the client, and since the client (evidently) round-trips unnormalised values unmodified, in 1.11 we could implement additional values for svn:executable (say, svn:executable=0755 and svn:executable=0775 to set only the respective unix permission bits); both 1.10 and 1.11 clients would round-trip the new values; 1.11 clients would map the new values to new semantics and 1.10 clients would map the new values to the old semantics (0777 &~ umask). That seems to be an argument in favour of raising a conflict. Cheers, Daniel (It's Friday, though, so I may have made a logical leap of faith along the way… ☺)