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

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

From: Christopher Ness <chris_at_nesser.org>
Date: 2005-08-23 16:39:24 CEST

On Tue, 2005-08-23 at 10:03 +0300, Flex wrote:
> > 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.
> There is one problem with this approach - the properties gets stored
> and distributed so there is a nice chance someone with CS system to
> checkout folder that has this property set from an NCS system.

Distribution is not a problem, it's a feature!

You can consider it doing the exact same thing as your switch, only once
the property is set for the file/dir the client (TSVN, svn, rapidsvn,
etc) handles the logic. No long does the user need to remember to
identify to the program that this file is NCS.

I have to flush out some more of this idea. Right now in my head it is
not really solving the problem, only moving the pre-commit script into
the logic of the client. That isn't a good solution.

I'll think some more on it, but the current suggestions (see thread
"[DESIGN] svn:resolve-case") all seem to be quite complicated.

There must be a cleaner solution.


Wireless Group
McMaster University
10:31:32 up 32 days, 20:24, 3 users, load average: 0.21, 0.13, 0.10
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 23 16:43:27 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.