From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/1] Fix a test on NTFS (and probably HFS+)
Date: Sat, 08 Jun 2019 07:43:43 -0700 (PDT) [thread overview]
Message-ID: <pull.151.git.gitgitgadget@gmail.com> (raw)
My colleague Jameson Miller once presented me with a nice puzzle why the
test suite failed on their system.
Turns out that it is possible in PowerShell to spell the directory with a
different case than on disk in cd <directory>, and subsequent calls to get
the current working directory will use that case, rather than what is
recorded on disk. And since case-insensitive filesystems are frowned upon in
the Linux world, Git's test suite was not prepared for such a scenario.
Johannes Schindelin (1):
t0001: fix on case-insensitive filesystems
t/t0001-init.sh | 12 ++++++++++++
1 file changed, 12 insertions(+)
base-commit: 8104ec994ea3849a968b4667d072fedd1e688642
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-151%2Fdscho%2Ffunny-cased-cwd-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-151/dscho/funny-cased-cwd-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/151
--
gitgitgadget
next reply other threads:[~2019-06-08 14:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 14:43 Johannes Schindelin via GitGitGadget [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.151.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.