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

Re: svn properties display bugs

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Sat, 10 Jan 2015 10:09:28 +0100

On 09.01.2015 23:10, cpengr wrote:
> Thanks for the prompt response.
> Re - "BUG 2":
>> The properties dialog shows the inheritance of properties correctly.
>> However what you expect it to do is to show how the properties *behave*.
>> Yes, the svn:ignore does not work recursively. But the property *is*
>> inherited - it's just not used that way.
> Sounds like a bad svn design decision to me. If child dirs don't behave
> as if they inherit svn:ignore from their ancestors, then why should they
> actually inherit it? Am I missing something?

As of svn 1.8, *all* properties are inherited. But inheritance does not
change the functionality, that's why svn:ignore does not ignore the
values it inherits, only those that are set directly.

> Even if there's a good svn rationale, what is the TSVN rationale? This
> mismatch between apparent/expected and actual behavior caused me
> considerable confusion as I tried to setup some custom ignoring. (I'm
> already having work around svn's lack of proper whitelisting...)

TSVN's rationale is that it shows what's actually happening with the
properties (it's the properties dialog after all). To configure the
ignore stuff, you have separate TSVN commands.

> Re - "BUG 1":
>> And while the svn:global-ignores property works like its data is
>> 'merged' down from all the inherited ones to the one that is set
>> directly on the folder, the TSVN properties dialog does not show those:
>> it only shows the inherited properties if the same property is not set
>> on that particular item.
>> Also, it only shows the inherited property that's closest to the item
>> that the dialog is shown for. - I just haven't found a good way UI-wise
>> to show multiple inherited properties.
> Why not just add additional rows? See attached proposal.

not a bad idea, but requires a lot more work. For example, what should
happen if a user tries to edit one of the inherited props? Right now,
that inherited prop is then simply set. But with multiple inherited
props and the directly set prop shown at the same time, you could end up
overwriting the directly set prop.


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest interface to (Sub)version control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-01-10 10:09:32 CET

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.