From: Johannes Sixt <j.sixt@viscovery.net>
To: Luc Bourhis <luc_j_bourhis@mac.com>
Cc: git@vger.kernel.org
Subject: Re: Trouble with case insensitive filesystem
Date: Wed, 15 May 2013 15:32:01 +0200 [thread overview]
Message-ID: <51938E51.5060900@viscovery.net> (raw)
In-Reply-To: <F0A0C92F-6D85-463E-9CB5-B9060BDA196B@mac.com>
Am 5/15/2013 10:40, schrieb Luc Bourhis:
> I work on a case insensitive filesystem and I have core.ignorecase set to true.
> ...
> So I thought it was a job for git filter-branch, ...
>
> However because of those two blobs, I have:
>
> ~> git status
> # modified: .../fourCircles.py
>
> and git filter-branch therefore refuses to run.
Make a commit that has neither file, run git filter-branch, then throw
away the commit with git reset --hard HEAD~.
-- Hannes
next prev parent reply other threads:[~2013-05-15 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 8:40 Trouble with case insensitive filesystem Luc Bourhis
2013-05-15 13:32 ` Johannes Sixt [this message]
2013-05-16 3:15 ` Luc Bourhis
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=51938E51.5060900@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=luc_j_bourhis@mac.com \
/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).