From: Jeff King <peff@peff.net>
To: Jason Pyeron <jpyeron@pdinc.us>
Cc: 'Git List' <git@vger.kernel.org>
Subject: Re: [cygwin] Re: Lack of case-sensitive filename handling with git 1.7.9-1 for Cygwin 64-bit
Date: Fri, 16 Aug 2013 09:21:01 -0400 [thread overview]
Message-ID: <20130816132101.GE20138@sigill.intra.peff.net> (raw)
In-Reply-To: <4D206B626EE941D28F6CB93E38293863@black>
On Fri, Aug 16, 2013 at 07:54:57AM -0400, Jason Pyeron wrote:
> > The interesting thing here is, if you try this the other way
> > around, you'll see the exact same effect. If you created the
> > above git repo with 64 bit git, everything works exactly as
> > in the 32 bit version and the two files are correctly recognized.
> >
> > I assume the format of the git database files depends on the
> > architecture. Therefore it's probably not advisable to use a
> > git repo created under 32 bit git with a 64 bit git and vice versa.
>
> Is this the best explanation for this?
If it is, that is a bug. There should be nothing architecture-dependent
in the index file.
In the test described, it would be worth double-checking that
core.ignorecase is set properly. Git will detect and set that option
when creating the repository based on a test of the filesystem. But it's
possible that there is some weirdness in the packaging or defaults of
the two builds.
It's also worth seeing if newer versions of git behave differently.
There were a lot of bugs in the case-insensitivity code that were fixed
in the late v1.7.x range. Though if I understand the test correctly, we
_shouldn't_ be using the case-insensitive code in the first place.
-Peff
prev parent reply other threads:[~2013-08-16 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGZiy71u1Ci_2Uw6jgAw3-9gCgwVrS1ae2Bpz9HCbnj2+EZexA@mail.gmail.com>
[not found] ` <20130816081743.GC2562@calimero.vinschen.de>
2013-08-16 11:54 ` [cygwin] Re: Lack of case-sensitive filename handling with git 1.7.9-1 for Cygwin 64-bit Jason Pyeron
2013-08-16 13:21 ` Jeff King [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=20130816132101.GE20138@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jpyeron@pdinc.us \
/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).