From: Kevin Daudt <me@ikke.info>
To: Robert Eisele <robert@xarg.org>
Cc: 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: Sat, 29 Apr 2017 22:18:13 +0200 [thread overview]
Message-ID: <20170429201813.GA19256@alpha.vpn.ikke.info> (raw)
In-Reply-To: <10d4f73b-b4bd-4cf8-5727-cdaf10ab713a@xarg.org>
On Sat, Apr 29, 2017 at 12:47:13PM +0200, Robert Eisele wrote:
> Hi,
>
> after having committed folders with lower case naming, I decided to rename
> them to upper-case names. Expecting git to detect them as renamings, it
> started a new parallel hierarchy with new files, which I had to add/commit.
>
> It was a kinda strange behavior, which I fixed by rename the folder to
> something completely different, commit and rename the folder again to the
> desired value.
>
> Is this an actual desired behavior or is it a bug?
>
> Robert
>
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.
Instead of storing it get relies on detecting what (parts of ) files got
renamed, copied etc.
next prev parent reply other threads:[~2017-04-29 20:18 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 [this message]
2017-05-01 1:47 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170429201813.GA19256@alpha.vpn.ikke.info \
--to=me@ikke.info \
--cc=git@vger.kernel.org \
--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.
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 NNTP newsgroup(s).