Issue #2036 is caused by the same issues being discussed here. See
http://subversion.tigris.org/issues/show_bug.cgi?id=2036
Garrett Rooney wrote:
> On 5/21/07, C. Michael Pilato <cmpilato@collab.net> wrote:
>> 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.
>
> The last time this came up I asked DLR about it and he said it was
> because the python config parser format (which we copied, and which
> we've always used as the docs for the format) has case insensitive
> keys.
That's not true anymore. The default for Python's ConfigParser is still
case-insensitive, but as of Python 2.1, there is a documented way to
make it case-sensitive (by setting an optionxform() attribute on the
ConfigParser instance). We confronted this issue in cvs2svn, which has
an option to use auto-props to set properties on files being converted.
See thread
http://subversion.tigris.org/issues/show_bug.cgi?id=2036
for a discussion. In the end, I punted on the issue by adding a second
option that lets the user decide whether to treat options
case-sensitively. The understanding over in cvs2svn-land was that once
SVN makes a decision we would match our behavior to SVN's.
Let me also remind people that auto-prop processing is a client-side
feature. Therefore it wouldn't be so preposterous to treat filename
patterns as case-sensitive on operating systems where filenames are case
sensitive, and case-insensitive on certain other lame OSs.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 23 20:47:38 2007