From: Eric Sunshine <sunshine@sunshineco.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
"Junio C Hamano" <gitster@pobox.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Александр Булаев" <aleks.bulaev@gmail.com>
Subject: Re: [PATCH] t: add clone test for files differing only in case
Date: Sun, 21 Jan 2018 13:47:09 -0500 [thread overview]
Message-ID: <CAPig+cT-oj2N978Qk3oQ_7wMOccAA80ws62UdFq3PvWkD6xKOg@mail.gmail.com> (raw)
In-Reply-To: <CACsJy8CpfVb546caxP-HGjk9uXa805uayF0A7oMzh+fzEFS_Qw@mail.gmail.com>
On Sun, Jan 21, 2018 at 6:50 AM, Duy Nguyen <pclouds@gmail.com> wrote:
> On Sun, Jan 21, 2018 at 3:33 AM, brian m. carlson
>> +test_expect_success 'clone on case-insensitive fs' '
>
> We have CASE_INSENSITIVE_FS prereq. Should we use it here? I know it
> does not harm running this test on case-sensitive filesystem, but the
> prereq could be useful for grepping.
I'd rather not hide it behind the CASE_INSENSITIVE_FS[1] prerequisite
since the test potentially could catch some sort of future regression
even on case-sensitive filesystems.
[1]: Todd Zullinger suggested the same:
https://public-inbox.org/git/CAPig+cSRN1zHc=zsO1Y_aQ_eO+sbsd0cq5iZ9hYz3ruK_E-0Dw@mail.gmail.com/
prev parent reply other threads:[~2018-01-21 18:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 20:55 git 2.16.0 segfaults on clone of specific repo Александр Булаев
2018-01-18 21:03 ` Randall S. Becker
2018-01-19 0:15 ` Eric Sunshine
2018-01-19 2:47 ` brian m. carlson
2018-01-19 3:06 ` Eric Sunshine
2018-01-19 3:39 ` Randall S. Becker
2018-01-19 3:40 ` brian m. carlson
2018-01-19 5:31 ` Duy Nguyen
2018-01-19 7:40 ` Eric Sunshine
2018-01-19 8:22 ` Duy Nguyen
2018-01-19 8:28 ` Eric Sunshine
2018-01-19 17:25 ` Todd Zullinger
2018-01-20 0:23 ` Eric Sunshine
2018-01-19 22:31 ` brian m. carlson
2018-01-20 0:15 ` Eric Sunshine
2018-01-20 0:23 ` brian m. carlson
2018-01-20 0:27 ` Eric Sunshine
2018-01-19 4:18 ` [PATCH] repository: pre-initialize hash algo pointer brian m. carlson
2018-01-19 7:54 ` Eric Sunshine
2018-01-19 19:24 ` Junio C Hamano
2018-01-19 21:48 ` Eric Sunshine
2018-01-19 22:25 ` Junio C Hamano
2018-01-19 23:14 ` brian m. carlson
2018-01-20 7:01 ` Junio C Hamano
2018-01-20 9:38 ` Eric Sunshine
2018-01-20 20:33 ` [PATCH] t: add clone test for files differing only in case brian m. carlson
2018-01-21 1:19 ` Eric Sunshine
2018-01-21 7:33 ` Junio C Hamano
2018-01-21 7:46 ` Eric Sunshine
2018-01-21 8:07 ` Eric Sunshine
2018-01-21 19:55 ` brian m. carlson
2018-01-21 11:50 ` Duy Nguyen
2018-01-21 18:47 ` Eric Sunshine [this message]
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=CAPig+cT-oj2N978Qk3oQ_7wMOccAA80ws62UdFq3PvWkD6xKOg@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=aleks.bulaev@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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).