Re: Bug: Git rename does not work if folder naming was changed from lower to upper case on OSX

From: Kevin Daudt <me@ikke.info>
Date: May 1, 2017, 17:07 UTC
Message-ID: <20170501170714.GA17703@alpha.vpn.ikke.info>
In-Reply-To: <xmqqshkpic0e.fsf@gitster.mtv.corp.google.com>

On Sun, Apr 30, 2017 at 06:47:29PM -0700, Junio C Hamano wrote:

Show 11 quoted lines

> Kevin Daudt <me@ikke.info> writes:
> 
> > Note that git does not store that files are renamed. So a remove + add
> > is the same as a rename in git. Only git status shows it when you for
> > example use git mv directly, but this information is lost on commit.
> 
> Are you sure about the last sentence?  I do not recall teaching
> anything special to "git status".  If "git status" says A was
> created by renaming B, and if you committed that state was-is, "git
> show" on the result commit _should_ say the same thing, I would
> think.

Yes, of course, you are right. Git status also detects a file being renamed instead of relying on it being recorded.

Show 5 quoted lines

> 
> > Instead of storing it get relies on detecting what (parts of ) files got
> > renamed, copied etc.
> 
> That statement I belieave is true.

Why are you reserved here?

Kevin.