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

Started by Junio C Hamano on May 1, 2017 · 2 messages from 2 authors · Last reply May 1, 2017

open the first message on its own page

Message details and related content
Kevin Daudt [off-list ref] 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.
Message details and related content
On Sun, Apr 30, 2017 at 06:47:29PM -0700, Junio C Hamano wrote:
Kevin Daudt [off-list ref] writes:
quoted
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.
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help