Re: [bug] Possible Windows 'git mv' bug

From: Aaron Gray <aaronngray.lists@gmail.com>
Date: Jan 31, 2016, 15:36 UTC
Message-ID: <CANkmNDfzxf045izkZV_Ps6_s0hA7q4kziu3u+BRexX-FOkgyWA@mail.gmail.com>
In-Reply-To: <CAEtYS8Qt1ewf3nAAiP_2ey5mV=9e3_To1fcaeV6f3+05uwHxgg@mail.gmail.com>

On 31 January 2016 at 15:05, Doug Kelly <dougk.ff7@gmail.com> wrote:

Show 20 quoted lines

> On Sun, Jan 31, 2016 at 8:50 AM, Johannes Sixt <j6t@kdbg.org> wrote:
>> Am 31.01.2016 um 15:03 schrieb Aaron Gray:
>>> I think I have found a possible difference in behaviour between
>>> Windows git commandline distro and Linux git
>>>
>>> basically If I do a :-
>>>
>>>      git mv logger.h Logger.h
>>>
>>> I get the following :-
>>>
>>>      fatal: destination exists, source=lib/logger.h,
>>> destination=lib/Logger.h
>>>
>
> Indeed.  And just to clarify, you'll get the same issue on OS X, where
> the filesystem is also case-preserving, not case-sensitive (by
> default, at least).  I've never tried using -f for this, but I'll
> usually use git mv twice to achieve the same result.  Annoying, but
> that way my local directory looks correct, too.

Ah, double up via a temporary name, cool hack !

Aaron