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

RE: TSVN 1.8.x prefers svn:global-ignores

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Tue, 15 Oct 2013 20:11:32 +0000

> On 15 October 2013 20:39, Simon Large <simon.tortoisesvn_at_gmail.com>
> wrote:
> On 15 October 2013 20:34, Simon Large <simon.tortoisesvn_at_gmail.com>
> wrote:
> On 15 October 2013 20:22, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 15.10.2013 21:00, Simon Large wrote:
> > I noticed this afternoon that when you have an svn:global-ignore and
> > an svn:ignore property set on a folder and you then look at the ignore
> > properties of a child folder, the svn:ignore is also listed as
> > inherited from the parent folder. Is that correct behaviour?
> does not happen for me.
> what properties do you have set exactly and what is showing in the
> properties dialog of the child folder?
> Stefan
> I'm still on 1.8.1 so it may be that.
> Set svn:global-ignore 'fred' on WC root folder Set svn:ignore 'bert' on WC
> root folder View properties of an immediate child folder.
> Not that both types of ignore are listed as inherited.
> My bad, it wasn't on the WC root, it was the next level down.
> I'll update to 1.8.2 soon and retry.
> Doing that now.
> Confirmed in 1.8.2. In fact it has nothing to do with global ignores. If I just set
> the svn:ignore property on a folder it is also on the child folder as an
> inherited property. But it's not real - items are not ignored in the child folder.
> Oh, I also have tsvn:logminsize set if that makes a difference.
> Simon

I'm pretty sure in 1.8.x ALL properties are inheritable... in other words, you can get a list of properties going up the path. However, subversion only looks up the chain for two properties currently, ie, svn:global-ignores and svn:autoprops.

This may be why all the properties are shown... even though they don't take effect. From the design wiki:

This is easy, there is no difference, there is no such thing as an "inheritable" property. Versioned properties, both Subversion's reserved properties and custom user properties, can be interpreted as inheritable, but otherwise function as they always have in terms of repository storage, setting properties, valid property names and values, etc.. What is proposed here is a new way of looking at the familiar versioned property. The only differentiation that is important as far as the design is this: Is a property value inherited or explicit? A path may have property 'PropName' explicitly set on it or property values may be inherited by a child path from some parent path(s) which also have 'PropName' explicitly set on them.
I assume TSVN is asking the API for the properties and using the equivalent of " --show-inherited-props" command line switch to retrieve them. So, technically those properties ARE inherited... they just don't take effect, because svn:ignore has to be EXPLICIT not inherited for it to be authoritative.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-10-15 22:11:40 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.