On Fri, Oct 14, 2016 at 4:21 PM, Branko Čibej <br...@apache.org> wrote:
> On 14.10.2016 09:17, Johan Corveleyn wrote:
>> FWIW, I think you have a valid usecase, though it's a bit unusual. Of
>> your proposed solutions, I think 1 and 2 are not possible (1 breaks
>> backwards compatibility
> On the other hand, I'd argue that the behaviour as described is a bug
> and that 1 is actually correct: an identical rule (identical glob
> pattern) in svn:auto-props property should completely override the rule
> from an inherited svn:auto-props property. Anything else leads to
> madness, as this thread shows.
Hm, yes, maybe you're right. In case of identical glob pattern in
svn:auto-props perhaps, yes.
Rereading the relevant section of the release notes , perhaps it
was even explicitly designed to behave that way, but maybe there is a
bug in the implementation. The release notes say:
Patterns defined in svn:auto-props property override any identical
patterns in the auto-props runtime config. When multiple
svn:auto-props properties apply to a file, the pattern from the
nearest inheritable property takes precedence. See this section of
design wiki for a full explanation.
FTR: I haven't yet tried to reproduce the problem Rob was seeing.
Maybe I'll try later.