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

Re: [PATCH]Why do we store svn config section options in a case insensitive way?

From: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2007-05-21 18:11:15 CEST

On Mon, May 21, 2007 at 11:57:57AM -0400, C. Michael Pilato wrote:
> Malcolm Rowe wrote:
> > On Mon, May 21, 2007 at 08:36:11PM +0530, Kamesh Jayachandran wrote:
> >> SVN config section option names are treated in a case insensitive way. This
> >> breaks autoprops setting on a patterns which differs only in case.
> >>
> >
> > The first statement is true; the second is a corollary of the first.
> > Your patch breaks config files that don't use lower case option names,
> > doesn't it?
> That's true, but to what degree do we care? We've only ever publicized our
> option names in lower-case form -- in samples, documentation, and
> discussion. So why would somebody choose to use a different form? Simply
> because they tried it and nothing fell completely over (for them)? Shame on
> them.

Well, we've said that we're compatible with the Python ConfigParser
format, and, as far as I'm aware, that has case-insensitive option names
(though it _does_ have case-sensitive section names, which we don't have).

This issue also bites authz. I'd be happy to change it, but I didn't
think that was an option. (See previous emails on dev@ from e.g.


  • application/pgp-signature attachment: stored
Received on Mon May 21 18:11:25 2007

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