Vincent Starre wrote:
> I really dont see what all the discussion is about, about should
> MyFile.c be converted into myfile.c. It seems simple in my mind:
> to a case-insensitive, they are the same file, so unless someone has
> specifically said svn mv, there is no reason to do anything "special":
> simply compare them in a case-insensitive manner and commit MyFile.c as
> it appears in the repos: myfile.c (or MYFILE.c, or whatever)
> if someone has said "svn mv", rename the file. There is no excuse for
> adding a new file or renaming a file without specific mv or add
> commands. There is no ability for a case-insensitive OS to treat them as
> seperate files, so there should be no attempt to support such.
As long as everybody uses a case insensitive file system there is indeed not
much of a problem (except that the svn server needs to know that file.c and
FILE.C are the same thing, (which is btw against standard URI specification)).
However in the all-use-case-insensitive-file-systems situation, this can be
solved.
The problem is however that svn is a x-platform solution, which means that
also case sensitive systems should be able to play in the same repository at
the same time.
You may have no problems at your case insensitive machine, a case sensitive
machine breaks if filenames change.
If I specify at a case sensitive file system how to build x.y in my Makefile,
and your machine decides to rename those files to x.Y and makefile, the build
tools at my case sensitive machine get hopelesly lost.
Also, I don't think forcing users of case sensitive machines into renaming
'wrongly' named files each time is going to work for a very long time.
In other words, this case sensitivity problem has to be solved such that *all*
clients work nicely together.
Albert
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 23 14:41:59 2005