git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Strapetz <marc.strapetz@syntevo.com>
To: Bryan Turner <bturner@atlassian.com>
Cc: j6t@kdbg.org, Git Users <git@vger.kernel.org>
Subject: Re: Unexpected ignorecase=false behavior on Windows
Date: Sun, 24 Jun 2018 12:07:32 +0200	[thread overview]
Message-ID: <c9a9167c-8528-c85a-e7aa-9197ab92e685@syntevo.com> (raw)
In-Reply-To: <CAGyf7-GvcN8EhMgtaZcDJNYNdfLwVH8HVBDmZqJU40nze0NSEA@mail.gmail.com>

On 22.06.2018 22:58, Bryan Turner wrote:
> On Fri, Jun 22, 2018 at 1:45 PM Marc Strapetz <marc.strapetz@syntevo.com> wrote:
>>
>> On 22.06.2018 19:36, Johannes Sixt wrote:
>>> 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.
>>
>> Sorry, it looks like my example was misleading. I'm actually questioning
>> current behavior in case of Windows repositories with core.ignorecase
>> initialized to false, like in following setup:
>>
>> $ git init
>> $ git config core.ignorecase false
>>
>> The repository is now set up to be case-sensitive on Windows. From this
>> point on, core.ignorecase won't change anymore and the repository will
>> be filled:
> 
> I don't think Hannes's point was _when_ you changed it; it was that
> you changed it _at all_.
> 
> Git on Windows is not designed to run with anything other than
> core.ignoreCase=true, and attempting to do so will cause unexpected
> behavior. In other words, it's not a behavior toggle so user's can
> request the functionality to work one way or the other; it's an
> implementation detail that `git init` and `git clone` set when a
> repository is created purely so they don't have to probe the file
> system each time you run a `git` command.
> 
> NTFS is case-preserving-but-case-insensitive by default[1]. So long as
> that's the case, the only mode for running Git on Windows is
> core.ignoreCase=true.
> 
> Hopefully this clarifies things!

Thanks, it does. In this case, I'd suggest to make this clear in the 
documentation, too. I've just sent a patch.

-Marc

  reply	other threads:[~2018-06-24 10:07 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
2018-06-22 20:45   ` Marc Strapetz
2018-06-22 20:58     ` Bryan Turner
2018-06-24 10:07       ` Marc Strapetz [this message]
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=c9a9167c-8528-c85a-e7aa-9197ab92e685@syntevo.com \
    --to=marc.strapetz@syntevo.com \
    --cc=bturner@atlassian.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    /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).