From: Jonathan del Strother <maillist@steelskies.com>
Date: Tue, 22 Jan 2008 20:54:51 GMT
Subject: Re: [RFC] File system difference handling in git
Message-ID: <57518fd10801221254u19888475s6192fedbbdd0b329@mail.gmail.com>
In-Reply-To: <3f4fd2640801220252q6a6557cdma4ca0a2c41223593@mail.gmail.com>

On Jan 22, 2008 10:52 AM, Reece Dunn <msclrhd@googlemail.com> wrote:
> This is what I am saying. For example, if you say:
>
>    git mv myfile.H myfile.h
>
> on a case sensitive filesystem (e.g. ext3), this will work, however on
> a case insensitive filesystem (e.g. ntfs) git would complain that the
> files are the same.
>
> The workaround is to say:
>
>    git mv myfile.H myfile.h.tmp
>    git mv myfile.h.tmp myfile.h
>
> but this is not ideal, especially if you are automating some move operations.
>

If I remember correctly, this fails when it comes to applying the
commit containing that move, at least on HFS+.  You could create 2
commits (one with the first mv, one with the second), and apply them
one at a time, but it's a pretty unpleasant workaround.