git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v4 0/1] Make abspath() aware of case-insensitive filesystems
Date: Fri, 18 Jan 2019 05:24:53 -0800 (PST)	[thread overview]
Message-ID: <pull.104.v4.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.104.v3.git.gitgitgadget@gmail.com>

It is completely legitimate these days to call git add with absolute paths.
Of course, on a case-insensitive file system, users rightfully expect the
argument to be handled case-insensitively, too. This patch makes it so.

Git for Windows carried this patch for over one and a half years already, I
think it is time to get it into git.git.

Changes since v3:

 * Fixed the oneline (it talked about core.fileMode when it really wanted to
   talk about core.ignoreCase!).

Change since v2:

 * Replaced MINGW prerequisite in the test by CASE_INSENSITIVE_FS. v1 was
   sent out without a change by mistake. Sorry.

Johannes Schindelin (1):
  abspath_part_inside_repo: respect core.ignoreCase

 setup.c        | 6 +++---
 t/t3700-add.sh | 7 +++++++
 2 files changed, 10 insertions(+), 3 deletions(-)


base-commit: 77556354bb7ac50450e3b28999e3576969869068
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-104%2Fdscho%2Fcase-insensitive-abspath-v4
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-104/dscho/case-insensitive-abspath-v4
Pull-Request: https://github.com/gitgitgadget/git/pull/104

Range-diff vs v3:

 1:  b935e11d21 ! 1:  3fb927fc77 abspath_part_inside_repo: respect core.fileMode
     @@ -1,6 +1,6 @@
      Author: Johannes Schindelin <johannes.schindelin@gmx.de>
      
     -    abspath_part_inside_repo: respect core.fileMode
     +    abspath_part_inside_repo: respect core.ignoreCase
      
          If the file system is case-insensitive, we really must be careful to
          ignore differences in case only.

-- 
gitgitgadget

  parent reply	other threads:[~2019-01-18 13:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21 11:32 [PATCH 0/1] Make abspath() aware of case-insensitive filesystems Johannes Schindelin via GitGitGadget
2018-12-21 11:32 ` [PATCH 1/1] abspath_part_inside_repo: respect core.fileMode Johannes Schindelin via GitGitGadget
2018-12-22 18:11   ` Carlo Arenas
2018-12-24 18:54     ` Johannes Schindelin
2018-12-24 22:34 ` [PATCH v2 0/1] Make abspath() aware of case-insensitive filesystems Johannes Schindelin via GitGitGadget
2018-12-24 22:34   ` [PATCH v2 1/1] abspath_part_inside_repo: respect core.fileMode Johannes Schindelin via GitGitGadget
2018-12-25 10:42     ` Torsten Bögershausen
2019-01-18 12:58       ` Johannes Schindelin
2018-12-24 22:56   ` [PATCH v3 0/1] Make abspath() aware of case-insensitive filesystems Johannes Schindelin via GitGitGadget
2018-12-24 22:56     ` [PATCH v3 1/1] abspath_part_inside_repo: respect core.fileMode Johannes Schindelin via GitGitGadget
2018-12-25  3:06       ` Junio C Hamano
2018-12-25  8:46         ` Junio C Hamano
2019-01-18 12:55           ` Johannes Schindelin
2019-01-18 13:24     ` Johannes Schindelin via GitGitGadget [this message]
2019-01-18 13:24       ` [PATCH v4 1/1] abspath_part_inside_repo: respect core.ignoreCase Johannes Schindelin via GitGitGadget

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=pull.104.v4.git.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).