From: Jeff King <peff@peff.net>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: dooagain <dooagain@protonmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Bug: git pull output and case sensitivity.
Date: Mon, 20 Mar 2023 13:16:02 -0400 [thread overview]
Message-ID: <20230320171602.GB2615782@coredump.intra.peff.net> (raw)
In-Reply-To: <20230319062239.w37x64knfhfapbsn@tb-raspi4>
On Sun, Mar 19, 2023 at 07:22:40AM +0100, Torsten Bögershausen wrote:
> On Sat, Mar 18, 2023 at 07:21:10PM +0000, dooagain wrote:
> > Thank you for filling out a Git bug report!
> > Please answer the following questions to help us understand your issue.
> >
> > What did you do before the bug happened? (Steps to reproduce your issue)
> >
> > I configured my git repository to ignore case by executing `git config core.ignorecase true` then I executed `git pull` multiple times.
>
> What do you mean by "I configured my git repository" ?
> The answer is already there, so let's re-rephrase it:
> Are you working on a case-insensitive file system ?
>
> What happens if you create a test directory, like this:
> mkdir test-case
> cd test-case
> git init
> git config --get core.ignorecase
I think this is kind of a red herring, isn't it? The bug report is about
refs, and I don't think those really respect core.ignorecase either way,
and inconsistencies are known to happen on case-insensitive filesystems
(because the refs are sometimes case-sensitive and sometimes not
depending on whether they are packed or loose in the filesystem).
So I think this is just a known gotcha, and the path forward is probably
a new ref storage format that doesn't rely on storing names directly in
the filesystem (reftable, or some system based on packed-ref slices).
-Peff
next prev parent reply other threads:[~2023-03-20 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 19:21 Bug: git pull output and case sensitivity dooagain
2023-03-19 6:22 ` Torsten Bögershausen
2023-03-20 17:16 ` Jeff King [this message]
2023-03-20 18:01 ` dooagain
2023-03-20 19:12 ` Torsten Bögershausen
2023-03-22 17:44 ` dooagain
-- strict thread matches above, loose matches on Subject: below --
2023-03-18 19:23 dooagain
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230320171602.GB2615782@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=dooagain@protonmail.com \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).