On 3/27/08, Anders J. Munch <ajm_at_flonidan.dk> wrote:
> Deven T. Corzine wrote earlier in the thread:
> > my suggestion is to have bare letters in the pattern be
> > case-insensitive, but letters in character classes be case-sensitive.
> > This is a little funky, but it means that "*.txt" could match any case,
> > while "*.[t][x][t]" would only match the lower-case extension. It's a
> > little confusing to have differing case-sensitivity in different
> > contexts in the glob, but probably less confusing than the current
> > behavior, in the grand scheme of things.
>
> +1. Simple and flexible. No new syntax that I will never be able to
> remember, because months or years pass between each time I use it.
>
> While not strictly 100% backwards compatible, I don't believe there's
> any real compatility issue. Anyone having a setup where lowercase
> means valuable source file, and uppercase means worthless build
> byproduct (or vice versa), has bigger problems than Subversion can
> solve.
Is that so? Have you ever used Unix? With case-sensitive filesystems?
I'm actually not all for changing the meaning of the current
interface: We even can't: it's a contract with our users we don't
change the meaning the interfaces until 2.0.
Bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-27 13:20:55 CET