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?
Agreed. > 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 done (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. Yes.