[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn:auto-props: property specified in a parent dir but not specified in a subdir

From: Branko Čibej <brane_at_apache.org>
Date: Tue, 18 Oct 2016 19:10:32 +0200

On 18.10.2016 18:46, Martin Edgar Furter Rathod wrote:
> On 10/18/16 16:38, Branko Čibej wrote:
>> On 18.10.2016 12:29, Daniel Shahaf wrote:
>>> Branko Čibej wrote on Tue, Oct 18, 2016 at 12:06:32 +0200:
>>>> If we change the behaviour so that a rule for a (case-insensitive)
>>>> pattern completely overrides a hierarchically previoius rule, we can
>>>> also introduce the concept of disabling auto-props rules; e.g., just
>>>> having a
>>>> *.txt =
>>>> could mean "do nothing with files matching '*.txt' from this point
>>>> onwards." I think that would be a quite valuable addition to the
>>>> auto-props feature set.
>>> This is a very compelling argument :-) However, I note that it,
>>> too, is
>>> backwards incompatible.
>> It is. I don't think there's any way we can /not/ make it backwards
>> incompatible, given the current implementation. Which is why I think we
>> should just admit that current behaviour is a bug.
>> Either that, or introduce a new property that behaves sensibly.
>> -- Brane
> Since it is "ini" format a section could be used to unset properties
> like this:
> *.txt = svn:eol-style=native
> [unset]
> *.txt = svn:executable
> Wouldn't this work?

The actual auto-props parser doesn't work that way. I'm not sure what
would happen but it's possible that current versions would fail because
the '[unset]' line is mising the '=' sign.

The whole idea behind the proposed format extension is to make sure that
current versions of SVN silently ignore the new rules.

-- Brane
Received on 2016-10-18 19:10:38 CEST

This is an archived mail posted to the Subversion Dev mailing list.