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

Re[6]: CaSe insensetive OS not handled well

From: Flex <flex_at_datecs.bg>
Date: 2005-08-23 09:03:05 CEST

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

... as it is now... it'll get at least better :)
Speaking of an automated client like TSVN, it can't "forget" :)

Can svn commit file.C and file.c a the same time, same folder now? And
does anyone uses that in fact? If not, can it be "disabled" so basicly
imitates this pre-commit hook?
Of course the pre-commit hook can be used too (when -NCS is not
specified) to guard against mistakes, just as it does it now, but
better if the whole system handles that.

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

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.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 23 09:07: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.