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

Re: Project properties: inheritance vs. copying

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Wed, 27 Apr 2011 10:26:53 +0100

On 27 April 2011 08:42, Hendrik Fuß <hendrik.fuss_at_gmail.com> wrote:
> Hi folks,
> I am a bit confused about the concept of project properties in TSVN. The following two excerpts from the manual seem to contradict each other:
> Source: http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-propertypage.html
> First: project properties are inherited
>> [...] project properties must be set on folders for the system to work. When you commit a file or folder the properties are read from that folder. If the properties are not found there, TortoiseSVN will search upwards through the folder tree to find them [...]
> Second: project properties are copied to new folders
>> When you add new sub-folders using TortoiseSVN, any project properties present in the parent folder will automatically be added to the new child folder too.
> Why would I want to have the project properties copied if I can rely on inheritance? I find that it makes project maintenance more difficult.
> Is there a rationale behind the copying function?

You can rely on inheritance _if_ you have the parent folder checked
out. If you create a new subfolder, say a new program under the main
project umbrella, and you don't copy the properties, someone else
could checkout just that one program without the parent and they would
not then get the parent's properties.


:       ___
:  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 2011-04-27 11:27:01 CEST

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