----- Original Message -----
From: "Tristan Seligmann" <tristan@quotemaster.co.za>
> > I would think that this would vastly slow down processing, because
every
> > time svn finds a file missing, it would have to then look again for an
> > uppercase representation.
>
> I suppose. I hadn't considered the performance issues; if this is the
> case, then clearly such a check would be unacceptable.
I think that performance issue is not so bad at all. Since Windows has
a filesystem which is case-insensitive Subversion should just compare
those path-strings case-insensitive on such OSes.
And I think performance isn't as important as _not_ loosing any data.
> > Don't use DOS apps??? Don't use Win32 and use a proper O/S??? <ducks>
Ok, don't use Win32 is a really bad advice. Or do you come to our office and
talk to our boss about switching OS? Would you succeed? Oh and don't forget:
all our development tools (compilers for Microprozessors, DSP's, ...) must
also
run under that other OS.
If you can do that then I'll gladly take your advice and switch to another
OS.
> I've run into the situation where MSVS.NET renames "resource.h" to
> "Resource.h" (or is it the other way around? I forget.). This caused some
> svn difficulties
Yes it does. I ran into the same problem and lost a whole bunch of data
because
of that...
Also, under Win2k there's a setting in the explorer to force filenames to be
created with a starting uppercase letter. So if you ever click twice (not a
doubleclick!)
on a file the explorer goes into "renaming mode". If you now just hit escape
to _not_
rename the file at all then explorer still changes the filename to a
starting uppercase
letter.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 7 16:29:00 2003