On 3/27/08, Anders J. Munch <ajm_at_flonidan.dk> wrote:
> From: Erik Huelsmann [mailto:ehuels_at_gmail.com]
> > > 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?
>
> Yes. I've seen .c/.C used to distinguish between C and C++. I've
> seen "makefile" and "Makefile" coexist to everyone's confusion. I
> understand the theoretical problem.
>
> Now, is there a practical problem? Do you know of any actual real
> life Subversion setups where widening the match of ignore patterns
> would cause breakage?
That's not the issue: the question we have to answer is: do you know
that they *don't* exist? Because if they do: we have a contract not to
change things.
> > 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.
>
> Nor am I in any hurry to change anything.
Well, in that case we're free to change the implementation if
developers reach consensus. However, I think that any features we
implement in the system should at least be consistent with the system
itself and if possible - after that - consistent with the OSes it runs
on. Since Subversion itself is case-sensitive, I still argue that the
default should be case-sensitive.
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 16:44:17 CET