git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Marc Strapetz <marc.strapetz@syntevo.com>
Cc: git@vger.kernel.org
Subject: Re: Unexpected ignorecase=false behavior on Windows
Date: Fri, 22 Jun 2018 19:36:05 +0200	[thread overview]
Message-ID: <1c7e338e-157b-fd2f-5eb1-01373f627acd@kdbg.org> (raw)
In-Reply-To: <c5abdd45-a919-96f6-8560-5fd943069f5e@syntevo.com>

Am 22.06.2018 um 14:04 schrieb Marc Strapetz:
> On Windows, when creating following repository:
> 
> $ git init
> $ echo "1" > file.txt
> $ git add .
> $ git commit -m "initial import"
> $ ren file.txt File.txt
> $ git config core.ignorecase false

This is a user error. core.ignorecase is *not* an instruction as in 
"hey, Git, do not ignore the case of file names". It is better regarded 
as an internal value, with which Git remembers how it should treat the 
names of files that it receives when it traverses the directories on the 
disk.

Git could probe the file system capabilities each time it runs. But that 
would be wasteful. Hence, this probe happens only once when the 
repository is initialized, and the result is recorded in this 
configuration value. You should not change it.

> Status results are:
> 
> $ git status --porcelain
> ?? File.txt
> 
> As on Unix, I would expect to see:
> 
> $ git status --porcelain
>   D file.txt
> ?? File.txt
> 
> Is the Windows behavior intended? I'm asking, because e.g. JGit will 
> report missing files, too, and I'm wondering what would be the correct 
> way to resolve this discrepancy? (JGit does not have 
> "ignorecase=true"-support at all, btw).

Then I don't think there is a way to remove the discrepancy.

-- Hannes

  reply	other threads:[~2018-06-22 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 12:04 Unexpected ignorecase=false behavior on Windows Marc Strapetz
2018-06-22 17:36 ` Johannes Sixt [this message]
2018-06-22 20:45   ` Marc Strapetz
2018-06-22 20:58     ` Bryan Turner
2018-06-24 10:07       ` Marc Strapetz
2018-06-25 16:34       ` Junio C Hamano
2018-06-25 17:38         ` Bryan Turner

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=1c7e338e-157b-fd2f-5eb1-01373f627acd@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=git@vger.kernel.org \
    --cc=marc.strapetz@syntevo.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).