From: Joshua Jensen <jjensen@workspacewhiz.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Jay Soffian <jaysoffian@gmail.com>,
Michael Haggerty <mhagger@alum.mit.edu>,
Gerd Knops <gerti@bitart.com>,
git@vger.kernel.org
Subject: Re: Possible bug with branch names and case sensitivity
Date: Wed, 23 Nov 2011 15:08:36 -0700 [thread overview]
Message-ID: <4ECD6EE4.6080702@workspacewhiz.com> (raw)
In-Reply-To: <CACBZZX4qs8-u33bZbrxYS1CrwjTQc=4YOk2SUjtYzL=vc9KYgA@mail.gmail.com>
----- Original Message -----
From: Ævar Arnfjörð Bjarmason
Date: 11/23/2011 1:50 PM
>
>
> Note that Git doesn't only have confusing behavior with refs on
> case-insensitive filesystems. The other day HFS+ users @ work had
> issues because of a case collision in the checked out tree, which
> confused git status et al.
Is core.ignorecase set to true? Is the repository shared with a case
sensitive file system?
I have a patch sitting around for 'git update-index --add' that fixes
some case insensitivity issues, especially when using Git Gui. This
patch complements the core.ignorecase patches I sent in the past.
-Josh
next prev parent reply other threads:[~2011-11-23 22:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 20:08 Possible bug with branch names and case sensitivity Gerd Knops
2011-11-21 19:18 ` Jay Soffian
2011-11-22 5:21 ` Michael Haggerty
2011-11-22 17:31 ` Jay Soffian
2011-11-23 8:54 ` Michael Haggerty
2011-11-23 20:50 ` Ævar Arnfjörð Bjarmason
2011-11-23 22:08 ` Joshua Jensen [this message]
2011-11-22 17:49 ` Junio C Hamano
2011-11-23 9:22 ` Michael Haggerty
2011-11-23 18:59 ` Junio C Hamano
2011-11-22 18:01 ` Junio C Hamano
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=4ECD6EE4.6080702@workspacewhiz.com \
--to=jjensen@workspacewhiz.com \
--cc=avarab@gmail.com \
--cc=gerti@bitart.com \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=mhagger@alum.mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.