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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Kevin Daudt <me@xxxxxxxxx> 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.

> Instead of storing it get relies on detecting what (parts of ) files got
> renamed, copied etc.

That statement I belieave is true.



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]