git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Kevin Daudt <me@ikke.info>
Cc: Robert Eisele <robert@xarg.org>, git@vger.kernel.org
Subject: Re: Bug: Git rename does not work if folder naming was changed from lower to upper case on OSX
Date: Sun, 30 Apr 2017 18:47:29 -0700	[thread overview]
Message-ID: <xmqqshkpic0e.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170429201813.GA19256@alpha.vpn.ikke.info> (Kevin Daudt's message of "Sat, 29 Apr 2017 22:18:13 +0200")

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.

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

That statement I belieave is true.

  reply	other threads:[~2017-05-01  1:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-29 10:47 Bug: Git rename does not work if folder naming was changed from lower to upper case on OSX Robert Eisele
2017-04-29 15:17 ` Torsten Bögershausen
2017-04-29 20:18 ` Kevin Daudt
2017-05-01  1:47   ` Junio C Hamano [this message]
2017-05-01 17:07     ` Kevin Daudt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqshkpic0e.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=me@ikke.info \
    --cc=robert@xarg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).