From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/1] t0001: fix on case-insensitive filesystems
Date: Wed, 19 Jun 2019 22:24:31 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1906192223560.44@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <CAN0heSrQ-AVui0OzpL7WGBzmdU4ignUsFxYqeXDtgR+CsDXbJw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1868 bytes --]
Hi Martin,
On Sun, 9 Jun 2019, Martin Ågren wrote:
> On Sat, 8 Jun 2019 at 16:45, Johannes Schindelin via GitGitGadget
> <gitgitgadget@gmail.com> wrote:
> >
> > From: Johannes Schindelin <johannes.schindelin@gmx.de>
> >
> > On a case-insensitive filesystem, such as HFS+ or NTFS, it is possible
> > that the idea Bash has of the current directory differs in case from
> > what Git thinks it is. That's totally okay, though, and we should not
> > expect otherwise.
>
> > +downcase_on_case_insensitive_fs () {
> > + test false = "$(git config --get core.filemode)" || return 0
>
> I think it would be worthwhile to add `--type=bool` to this git-config
> call. See, e.g., the FILEMODE prereq in t/test-lib.sh. From my
> understanding, this check would regress if someone did s/false/no/ in
> builtin/init-db.c, so this check is perhaps not as robust as it could
> be. (Now, as for *why* someone would do such a change...)
>
> I do wonder if this is the right way to check for a case-insensitive
> filesystem. According to git-config(1), this variable tells whether "the
> executable bit of files in the working tree is to be honored". I can see
> how this property could correlate with the filesystem being
> case-insensitive, but from git-config(1), I would have expected
> core.ignoreCase to be queried instead.
Oh my, you're right. I do not know how the filemode slipped in...
Thanks!
Dscho
> You're no doubt a lot more familiar with filesystem case-insensitivity and
> how it interacts with Git than I am. Any light you could shed on this
> would be much appreciated.
>
> > + for f
> > + do
> > + tr A-Z a-z <"$f" >"$f".downcased &&
> > + mv -f "$f".downcased "$f" || return 1
>
> Makes sense. Good error-handling.
>
> > + done
> > +}
>
> Cheers
> Martin
>
next prev parent reply other threads:[~2019-06-19 20:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 14:43 [PATCH 0/1] Fix a test on NTFS (and probably HFS+) Johannes Schindelin via GitGitGadget
2019-06-08 14:43 ` [PATCH 1/1] t0001: fix on case-insensitive filesystems Johannes Schindelin via GitGitGadget
2019-06-09 19:23 ` Martin Ågren
2019-06-19 20:24 ` Johannes Schindelin [this message]
2019-06-09 20:13 ` brian m. carlson
2019-06-10 16:32 ` Junio C Hamano
2019-06-19 20:17 ` Johannes Schindelin
2019-06-21 19:33 ` Ævar Arnfjörð Bjarmason
[not found] ` <pull.151.v2.git.gitgitgadget@gmail.com>
[not found] ` <c2fdcf28e725c91a1a48c34226223866ad14bc0a.1560978437.git.gitgitgadget@gmail.com>
2019-06-21 14:34 ` [PATCH v2 " Johannes Schindelin
2019-06-21 17:31 ` Junio C Hamano
2019-06-24 10:13 ` Johannes Schindelin
2019-06-24 17:09 ` Junio C Hamano
2019-06-24 17:38 ` Johannes Schindelin
2019-06-24 19:22 ` Junio C Hamano
[not found] ` <pull.151.v3.git.gitgitgadget@gmail.com>
[not found] ` <1f0ceee8687e9032a7777f764b34b1c9ccc68f38.1561379363.git.gitgitgadget@gmail.com>
2019-06-24 17:40 ` [PATCH v3 " Johannes Schindelin
2019-06-24 18:55 ` Junio C Hamano
2019-06-25 10:50 ` vger vs GitGitGadget, was " Johannes Schindelin
2019-06-25 19:42 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1906192223560.44@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=martin.agren@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).