From: Kevin Daudt <me@ikke.info>
To: Junio C Hamano <gitster@pobox.com>
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: Mon, 1 May 2017 19:07:14 +0200 [thread overview]
Message-ID: <20170501170714.GA17703@alpha.vpn.ikke.info> (raw)
In-Reply-To: <xmqqshkpic0e.fsf@gitster.mtv.corp.google.com>
On Sun, Apr 30, 2017 at 06:47:29PM -0700, Junio C Hamano wrote:
> 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.
>
> > 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.
prev parent reply other threads:[~2017-05-01 17:07 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
2017-05-01 17:07 ` Kevin Daudt [this message]
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=20170501170714.GA17703@alpha.vpn.ikke.info \
--to=me@ikke.info \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).