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

Re: [RFC] svn propset should require 'force' to set unknown svn: propnames

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Mon, 19 Nov 2012 09:23:30 -0500

On 11/19/2012 09:13 AM, Daniel Shahaf wrote:
> Another thing we could do is warn when unrecognised options are found in
> the config file (~/.subversion/*) or in the --config-option command-line
> option.
>
> This would be an independent improvement, i.e., it neither blocks nor
> is blocked by the propset improvements in #4261.

As regards the config files, -0 (tending towards -1). The runtime
configuration area is not release-version-specific. Folks like myself who
keep their ~/.subversion under version control and use it across many
different clients (which may be running different versions of Subversion)
could be constantly irritated by such warnings. And of course, we devs
would be likely to run into such things often, too. Besides, the config
files are generated as templates -- you'd have to work extra hard to botch
the spelling of an option name there. :-)

As for warning on bogus --config-option input ... I'm closer to +0 or +1 there.

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development

Received on 2012-11-19 15:24:08 CET

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