From: "Torsten Bögershausen" <tboegi@web.de>
To: Kevin Coleman <kevin.coleman@sparkstart.io>, Jeff King <peff@peff.net>
Cc: Bryan Turner <bturner@atlassian.com>, Git Users <git@vger.kernel.org>
Subject: Re: folder naming bug?
Date: Tue, 03 Feb 2015 09:40:29 +0100 [thread overview]
Message-ID: <54D0897D.4050101@web.de> (raw)
In-Reply-To: <26FB4384-1027-436F-84C5-91C6CC4D27EA@sparkstart.io>
On 02/03/2015 07:23 AM, Kevin Coleman wrote:
> Awesome reply! That makes sense. So basically if I accidentally capitalize a folder name and commit it, I need to be very careful when I correct it. Definitely ran into this problem with my repo and ‘lost’ a few commits before I noticed something was off.
>
> -Kevin Coleman
(Please no top-posting)
According to my experience setting core.ignorecase false
may cause the user to loose commits.
Can you reproduce the problem ?
with core.ignorecase false (Which is wrong)
with core.ignorecase true (You shouldn't loose anything)
next prev parent reply other threads:[~2015-02-03 8:41 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 [this message]
2015-02-03 8:34 ` Torsten Bögershausen
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=54D0897D.4050101@web.de \
--to=tboegi@web.de \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=kevin.coleman@sparkstart.io \
--cc=peff@peff.net \
/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).