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.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html