Jonathan Malek wrote:
>When doing a check-out of these two files, the filesystem will see
>them as the same file (case-insensitive), and the client will
>effectively checkout the first one, then attempt to overwrite it with
>the second (from my tests, the lowercase one remains). The
>filesystems DO respect the case of the file for display, such that a
>file can be "move"d from Something.txt to something.txt.
>
>With files, it's a silent operation--update, and a file disappears
>(overwritten). With directories, it's a little noisier:
>c:\>svn update
>A Docs
>"svn: Failed to add directory 'docs' : object of the same name already exists".
>
>
I'm still not sure what you think Subversion should do differently.
Somehow choose one or the other file or directory to "win" in such a
case? That would lead to data loss.
What you need to do is prevent such scenarios from occurring in the
first place by installing a hook script which prevents a file or
directory from being added if one with a name that is different only in
case already exists, if any of your Subversion clients are on
case-insensitive filesystems. Such hook scripts already exist in the
contrib area.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 15 05:05:56 2005