From: "Torsten Bögershausen" <tboegi@web.de>
To: Kevin Coleman <kevin.coleman@sparkstart.io>,
Bryan Turner <bturner@atlassian.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: folder naming bug?
Date: Tue, 03 Feb 2015 09:34:02 +0100 [thread overview]
Message-ID: <54D087FA.8030707@web.de> (raw)
In-Reply-To: <06E0624C-2484-476D-A32F-B586062EC230@sparkstart.io>
On 02/03/2015 05:52 AM, Kevin Coleman wrote:
> ====
> Yes, I am on a Mac. I just tried that, but I don’t think that completely fixed it. As you can see it tracks “foo/bar.md” and then it tracks “Foo/bar.md”. It still tracks both “foo” and “Foo” even tho only “Foo” exists in my dir after the rename.
You asked Git to track Foo/bar.md and the file system says "yes, it's here"
When you rename Foo/ into foo/, the file system still says "Foo/bar.md"
is here.
You need to tell git about the rename :
git mv Foo/bar.md foo/bar.md
Why does anybody think that setting "core.ignorecase false" will
convince the file system
to become case insensitive ?
prev parent reply other threads:[~2015-02-03 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 1:56 folder naming bug? Kevin Coleman
2015-02-03 4:37 ` Bryan Turner
2015-02-03 4:52 ` Kevin Coleman
2015-02-03 5:23 ` Jeff King
2015-02-03 6:23 ` Kevin Coleman
2015-02-03 8:40 ` Torsten Bögershausen
2015-02-03 8:34 ` Torsten Bögershausen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54D087FA.8030707@web.de \
--to=tboegi@web.de \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=kevin.coleman@sparkstart.io \
/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).