SVN will treat a check-in of a file Something.txt as a separate entry
from something.txt--examining the repository will show two separate
files, Something.txt and something.txt.
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".
On 7/14/05, Toby Johnson <toby@etjohnson.us> wrote:
> Bryan Dyck wrote:
>
>
> On 14-Jul-05, at 1:16 AM, Martin Tomes wrote:
>
> I would like to make a plea on behalf of Windows users everywhere.
>
> Please can there be proper handling of case insensitive files systems in
> the client. The server side can be handled by a hook script, the client
> cannot. Given the huge number of users of Subversion on the Windows
> platform surely this must be considered important.
>
> In a related vein, OS X's default filesystem is case-insensitive as well
> (although case-preserving), so OS X users would also stand to benefit from
> any improvements here in the SVN client.What exactly are you two talking
> about? What does SVN not currently do correctly on these filesystems?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 15 01:23:21 2005