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

Re: Bikeshed: configuration override order

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sat, 7 Aug 2010 13:34:59 +0300

Stefan Sperling wrote on Fri, Aug 06, 2010 at 21:51:37 +0200:
> Why do we have settings in the individual client config that all users
> would want to share anyway?
> So maybe having auto-props in the config is part of the problem? What about
> having an svn:auto-props property at the parent directory, specifying
> autoconf settings for its direct children?


> Too inconvenient to set up due to lack of recursive property support?
> Would 'svn propset -R' do to configure auto-props for an entire subtree
> like '/trunk'?

Or do we want something like "this is a branch root" property? Or do we
want some "look in parent" value for svn:auto-props?

    for i in $subdirs_of_trunk; do
        svn propset --symlink svn:auto-props ../ $i

(and then, what happens if you checkout a proper subfolder of trunk ---
e.g., ^/trunk/subversion --- without checkouting its parent, and attempt a
propset? Not unsolvable, but needs to be thought of.)

> Once those properties were set up and configured, users
> could mostly forget about auto-props unless the default auto-props need
> to be changed. Not whenever they start working on a different client
> computer, as they do today.

Received on 2010-08-07 12:37:24 CEST

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

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