RE: [PATCH]Why do we store svn config section options in a caseinsensitive way?

From: Kamesh Jayachandran <kamesh_at_collab.net>
Date: 2007-05-22 20:22:00 CEST

>+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.
>
>Regards,
>Malcolm

Thanks all. Attaching the patch in the direction suggested by Justin.

With regards
Kamesh Jayachandran

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

text/x-patch attachment: autoprops.patch

text/x-log attachment: autoprops.log

Received on Tue May 22 20:24:03 2007

This message: [ Message body ]
Next message: Paul Burba: "RE: svn commit: r25068 - in trunk/subversion: libsvn_client libsvn_fs_util libsvn_subr tests/libsvn_subr"
Previous message: Aleksey Nogin: "RFE: "svndumpfilter mv""
In reply to: Malcolm Rowe: "Re: [PATCH]Why do we store svn config section options in a case insensitive way?"
Next in thread: Carlos Alberto Costa Beppler: "Re: [PATCH]Why do we store svn config section options in a caseinsensitive way?"
Reply: Carlos Alberto Costa Beppler: "Re: [PATCH]Why do we store svn config section options in a caseinsensitive way?"
Reply: Daniel Rall: "Re: [PATCH]Why do we store svn config section options in a caseinsensitive way?"

Contemporary messages sorted: [ By Date ] [ By Thread ] [ By Subject ] [ By Author ] [ By messages with attachments ]