> Changing case locally results in even worse problems; if you
> have a file
> called 'FILE' but subversion has a versioned file called
> 'file' it will
> identify 'FILE' as unversioned (which is fine), but not realize that
> operations on 'file' will actually affect 'FILE'.
> Specifically, it will
> try and check 'file' out again, silently overwriting 'FILE',
> as opposed
> to something like the 'obstructed' message one would get with an
> existing 'file' that is unversioned (although obviously such a file
> couldn't exist in this specific situation).
>
> (If you're wondering how this sort of thing happens, remember
> that any
> DOS - actual DOS, not Win32 console - program writing out a file will
> change the case to uppercase...)
There must be some way that subversion could be written such that it could
be forced to anticipate these case issues and do the intelligent thing. For
example, and this is silly but makes my point, spawn a command session, do a
"dir /b", capture the result, check the case of the filenames for possible
conflicts, then do the right thing (no silently overwriting FILE!).
As long as this is an optional mode, forget performance hits for this, I
don't care if the command takes ten times as long if it correctly handles
case when I need it to.
--- Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 19 15:13:31 2003