[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Ignore patterns should not be case sensitive (usability)

From: Anders J. Munch <ajm_at_flonidan.dk>
Date: Fri, 28 Mar 2008 16:29:00 +0100

Erik Huelsmann wrote:
> > 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: ...

You don't know that because it isn't true. I can disprove it by
counterexample.

> >
> > 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).

That makes no sense. Without knowledge of the client side file system
Subversion wouldn't be able to read and write files, navigate
directories etc. The subversion client library is to a large part a
mediator layer between the repository server and the client side file
system. It is positively loaded with knowledge and assumptions about
the client-side file system.

Subversion limits itself to using a portable subset of client side
file system features, of course, so you can't exactly match the
expectations of all platforms, because that would require a lot of
platform-specific code. But what you can do is find a common path
that works reasonable well with a wide variety of platforms, and
indeed, isn't that what Subversion developers always have done?

- Anders
Received on 2008-03-28 16:29:25 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.