On Wed, Nov 7, 2012 at 11:48 AM, Stefan Sperling <s...@elego.de> wrote: > On Wed, Nov 07, 2012 at 09:40:48AM +0100, Johan Corveleyn wrote: >> I haven't tested, but wouldn't something like 'svn add --config-option >> config:miscellany:enable-auto-props=no' do something like that? > > Nobody wants to type that! :) > > And you realise the --no-auto-props option already exists in 1.7?
Oops, learned something new :-). I thought Daniel was making it up. > It's reasonable to make this existing option override the svn:auto-props > property, just like --no-ignores overrides the svn:ignore property. Indeed. A related question then (sorry if this is in the spec or a mail-thread -- I have read a lot of it, but haven't gone through all the details): will a setting of enable-auto-props=no in the config file of the user's runtime config ignore the svn:auto-props? How about when it's set as a command line option, like my example above? On first sight, this seems to me the best behavior: - If enable-auto-props is not set (which is normally the case when you have a fresh install of svn): defaults to "no" for runtime config (miscellany), but still applies the svn:auto-props settings. - If enable-auto-props = no -> no auto-props are applied, not even the svn:auto-props. - If enable-auto-props = yes -> all are applied. - The above rules apply wherever the enable-auto-props is set (I mean: the existing priority rules are applicable) The first rule introduces an inconsistency between auto-props-in-config and svn:auto-props, but for a very good reason: it allows svn:auto-props to impact freshly installed svn clients, no need for all end users to go fiddling in their config file to enable the auto-props feature. (sorry if I'm rehashing old arguments/specs/discussions ... I claim not-able-to-follow-everything-ness :-)) -- Johan
