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

Re: Re[4]: CaSe insensetive OS not handled well

From: Christopher Ness <chris_at_nesser.org>
Date: 2005-08-22 23:13:43 CEST

On Mon, 2005-08-22 at 23:32 +0300, Flex wrote:
> > Invitations like above are often the result of these conversations. But
> > for whatever reason, no one seems to have the skills or ability to
> > architect and implement a clear and consistent solution. That is -- not
> > just a cheap hack to put in a client switch.
> :)

That sounded harsh. I want to take a few bytes to justify my comment.

The first user who forgets to use the -NCS flag/switch and commits a
case sensitive derivative of a working copy file breaks the system for
everyone else. Right? Because backwards compatibility must be
maintained this is easily possible - no need to write a rouge client.

It also involves an understanding of your platform and your file system
for the client _and_ server machine you are working with.

I would be more open to a new property called "svn:case-insensitive"
which acted like the "svn:executable" property. If set the client
performs a well defined, deterministic action on the file/directory.
This action could be munging all the file names to lower case, upper
case or something else.

NOTE: There are some serious failure cases that need to be dealt with in
this proposal. Like if two files produce a name clash when the action
is performed. What do you do?

Anyway, best of luck.

PGP Public Key: http://www.nesser.org/pgp-key/
16:53:45 up 9:02, 2 users, load average: 0.24, 0.25, 0.19

Received on Mon Aug 22 23:13:54 2005

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.