On Thu, Jan 5, 2012 at 3:23 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
>> The approach TortoiseSVN and some other clients take does work pretty
>> nicely but I also think they reveal the short comings in using
>> properties. For convenience, TortoiseSVN does not force you to set
>> these properties on every folder and instead will walk to the root of
>> your WC to find them, but then this also exposes the problem that if
>> you did not checkout the folder that has those properties you are back
>> to square one. That is why I believe it makes sense for SVN to
>> support it natively using an approach something like described in the
>> wiki. Or at least weigh that approach versus using properties within
>> the repository. Perhaps properties are the way to add the deferred
>> feature of supporting overrides based on path?
> overrides based on path - do you mean that properties would be inherited,
> i.e., child items inherit the properties of the parent item(s)?
Yes. Presumably. Imagine the ASF repository with hundreds of
autonomous projects. Ideally each project could have its own settings
but still live in the same repository.
> And the best advantage of all:
> users could set/modify the properties with their clients. No need to contact
> the administrator and have him do it - believe me, Admins will very soon get
> annoyed if such changes/modifications happen often.
That is good for some settings, but not necessarily all of them,
although I suppose an Admin could use a pre-commit hook script to
prevent clients from committing settings changes if they are not
Received on 2012-01-05 21:27:42 CET