On 3/28/08, Anders J. Munch <ajm_at_flonidan.dk> wrote:
> Erik Huelsmann wrote:
> > On 3/27/08, Anders J. Munch <ajm_at_flonidan.dk> wrote:
> > > 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?
>
> Indeed not. Nor does anyone know for sure that there are no ignore
> patterns in the wild of the form
> ^option: [a-z0-9]+
> I take it you reject that proposal on the same grounds?
Exactly.
> Either you don't change anything at all or you allow some
> propertionality in the burden of evidence.
No. Because I know there are patterns which won't exist:
/option: ...
is guaranteed not to exist: '/' can't be part of a file name.
> > 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.
>
> Ignore patterns are used for talking about client-side files, notably
> files that are not (yet) under Subversion's control. Consistency with
> client-side file system rules and conventions is what matters here.
Subversion doesn't have knowledge of the client side file system and
as far as I can see, neither will it be able to grow any. So, since we
can't be consistent with the host platform, we'll have to be
consistent with ourselves (which is 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-28 15:20:51 CET