mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ax Da" <>
Subject: Git config "ignorecase = true" has issues
Date: Fri, 19 Apr 2019 21:28:32 +0200	[thread overview]
Message-ID: <trinity-3f1323ca-ca26-46c1-8757-b30bb495bd3a-1555702112240@3c-app-gmx-bs44> (raw)

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.

Axel Dahmen

             reply	other threads:[~2019-04-19 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-19 19:28 Ax Da [this message]
2019-04-24 19:11 ` Git config "ignorecase = true" has issues Torsten Bögershausen
  -- strict thread matches above, loose matches on Subject: below --
2019-05-05 10:11 Ax Da
2019-05-18 12:58 Ax Da
2019-05-18 16:38 ` Johannes Sixt
2019-05-21  2:31   ` 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-3f1323ca-ca26-46c1-8757-b30bb495bd3a-1555702112240@3c-app-gmx-bs44 \ \ \

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