mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ax Da" <>
To: unlisted-recipients:; (no To-header on input)
Subject: Re: Git config "ignorecase = true" has issues
Date: Sat, 18 May 2019 14:58:40 +0200	[thread overview]
Message-ID: <trinity-4a160867-2036-4f8a-8363-7bf2e021d840-1558184320864@3c-app-gmx-bs48> (raw)

Anyone who likes to fix this issue?

Gesendet: Sonntag, 05. Mai 2019 um 12:11 Uhr
Von: "Ax Da" <>
An: unlisted-recipients:;
Betreff: Re: Git config "ignorecase = true" has issues
Thanks for replying. Do you know how the query you mentioned ("Do we have a file named "file.txt" on disk?") is implemented in git?

I'd suggest to use the C++ Windows API function FindFirstFileW() and then manually compare the result with the queried file name, like:

bool fileExists(const WCHAR_T *fileName, bool ignoreCase)
  WIN32_FIND_DATAW fileData;
  bool fileExists = false;
int (*strCmp)(const wchar_t *string1, const wchar_t *string2, size_t count)
= ignoreCase ? _wcsnicmp : wcsncmp;

  if (FindFirstFileW(fileName, fileData) != INVALID_HANDLE_VALUE)
    if (!strCmp(fileName, fileData.cFileName, wcsnlen(fileName, MAX_PATH) + 1)) fileExists = true;
  return fileExists;


Gesendet: Mittwoch, 24. April 2019 um 21:11 Uhr
Von: "Torsten Bögershausen" <>
An: "Ax Da" <>
Betreff: Re: Git config "ignorecase = true" has issues
On Fri, Apr 19, 2019 at 09:28:32PM +0200, Ax Da wrote:
> We're working on Windows machines and have been experiencing issues with the current implementation of Git with config setting "core.ignorecase = true" (which is the default on Windows machines and repositories created on Windows machines):
> Renaming files in a repository by only changing their case (changing a capital letter to its small equivalent and vice versa) is ignored by Git. Git retains the original case in the repository and all contributors will continue to see the ole file name which leads to confusion and issues with Open Source tools programmed to not ignore file name case.
> Currently there is no way to convey the new file name (only differing in case) to Git when "core.ignorecase = true".
> Hence, I propose to alter the behaviour of Git when "core.ignorecase = true": A repository's file name changes should be recognized as a RENAME operation and be propagated to the repository even when the new file name only differs from the old file name in case.

You can rename files like this:
git mv File.txt file.txt
git commit

and Git will record the changes.

The main problem is, that after the rename, and may be on another machine after a pull,
Git checks with the file system, if any updates in the working tree are needed.
In human speech, Git asks the file system:
Do we have a file named "file.txt" on disk ?
And Windows answers: Yes we have.
Even if the file is named "File.txt" and Git asks for "file.txt".

You can try it yourself.
cat File.txt
under the Git shell (bash)
type File.txt
under cmd.exe

That is how it is.

If you really need the updated name "file.txt", you can delete all files in the worktree
rm -rf *
followed by
git reset --hard

But in any case, run
git status
before and make sure that your working tree is clean.

> Thanks,
> Axel Dahmen

             reply	other threads:[~2019-05-18 12:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-18 12:58 Ax Da [this message]
2019-05-18 16:38 ` Git config "ignorecase = true" has issues Johannes Sixt
2019-05-21  2:31   ` Torsten Bögershausen
  -- strict thread matches above, loose matches on Subject: below --
2019-05-05 10:11 Ax Da
2019-04-19 19:28 Ax Da
2019-04-24 19:11 ` Torsten Bögershausen

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-4a160867-2036-4f8a-8363-7bf2e021d840-1558184320864@3c-app-gmx-bs48 \ \ \

* 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

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).