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

Re: [Issue 4362] New - Version-spanning configuration files should note release versions in which options appeared/changed.

From: Daniel Shahaf <danielsh_at_elego.de>
Date: Fri, 3 May 2013 20:09:47 +0300

cmpilato_at_tigris.org wrote on Fri, May 03, 2013 at 07:48:07 -0700:
> It is not unreasonable to think that my runtime configuration area could have
> been created by a Subversion 1.7 client, but that from time to time I need to
> use a 1.6 client on the same machine. Users in such situations might be
> confused as to why, when they modify a new-in-1.7 config option (in the file, or
> via the --config-option switch), it seems to have no effect on their 1.6
> client's behavior.

Couldn't we warn (non-fatally) on unrecognised options? i.e., when an
unrecognised section name or option name is seen in the config file,
issue a warning to stderr and proceed.

(We should probably avoid printing a warning if the key is subsequently
referred to in an %()s interpolation.)

If we implement that in 1.9, then if you use a 1.9 client on
a config-dir containing a configuratino written for 1.10, you will get
runtime warnings for the new-in-1.10 options you use.

Seems that's orthogonal to #4362, though.
Received on 2013-05-03 19:11:08 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.