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

Re: CaSe insensetive OS not handled well

From: Vincent Starre <vstarre_at_comcast.net>
Date: 2005-08-22 23:39:47 CEST

Christopher Ness wrote:

>Did you really just map *.c = *.c in your above example? Because that
>would be wrong IMO. Imagine ( main.c = function.c ).
>Although I know what you are trying to suggest: ( main.c = Main.c ) that
>is not what is implied by the kleene star above.
>
>
if I am not mistaken, the way windows utils tend to handle asterisks,
that actually would be correct.
Windows asterisks and bash asterisks are not the same.

>Not to be rude, but SVN allows you to reject mixed case commits with a
>hook script, but it will _never_ modify the transactions you create for
>commits.
>
>
>
And as far as a case-insensitive OS is concerned, no modification would
take place. Really, the idea of
saying that File.c and file.c are two seperate files when the OS says
they are not is a flaw. That is: it is
breaking the transaction to assert such a falsehood.

I presume such wild notions as "I think file.c and File.c are the same"
will become more accepted once true
moves/renames are implimented- if I dont say "svn mv" it can be assumed
that I want the case that's in the repos,
if I /do/ say "svn mv" it can be assumed that I want the case that's in
my working copy. If my OS is one that cares
about the case of filenames, it can be assumed that the files really are
seperate.

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