[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: Norbert Unterberg <nunterberg_at_gmail.com>
Date: 2007-05-22 07:44:00 CEST

2007/5/21, Malcolm Rowe <malcolm-svn-dev@farside.org.uk>:
> On Mon, May 21, 2007 at 12:24:29PM -0400, C. Michael Pilato wrote:
> > > Silently ignoring config options because the case is wrong seems bad, IMO.
> > >
> > > I think it'd be better to normalize filenames before checking the
> > > autoprops code. This would mean that we lose case-sensitivity on the
> > > applicability of the autoprops, but I view that as a far lesser evil.
> > > -- justin
> >
> > Yeah, I think I have to agree. For one thing, it's easy to document that
> > our autoprop application is done case-insensitively. But secondly, folks
> > might actually *prefer* this most of the time, even, especially if their
> > repositories are prone to winding up with upper-cased filenames thanks to
> > some Windows software.
> >
>
> +1. Given the inability to have different rules for differently-cased
> versions of a filename, I don't see why we shouldn't ignore case when
> determining the applicability of an autoprop rule too.

BTW, what is the encoding of config files? UTF-8 or the user's local
code page? Because encoding matters when doing text conversions.

Norbert

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 22 07:44:13 2007

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