From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, szeder.dev@gmail.com, newren@gmail.com,
Derrick Stolee <dstolee@microsoft.com>
Subject: Re: [PATCH 1/1] sparse-checkout: respect core.ignoreCase in cone mode
Date: Fri, 13 Dec 2019 14:02:51 -0800 [thread overview]
Message-ID: <xmqqeex7hoj8.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <d1b11424-db8b-e13c-e896-923d74b3d531@gmail.com> (Derrick Stolee's message of "Fri, 13 Dec 2019 14:40:58 -0500")
Derrick Stolee <stolee@gmail.com> writes:
> On 12/13/2019 2:05 PM, Junio C Hamano wrote:
>> Derrick Stolee <stolee@gmail.com> writes:
>>
>>> If you have a plan for that branch and the merge status of those
>>> commits, then I'm happy to re-target my PR against 'next' or
>>> an equivalent branch.
>>
>> This change does not make much sense without the cone-mode topic,
>> no?
>
> I'm saying it should go on top, as a new branch that depends on
> ds/sparse-cone. Sorry for not making that clear.
I thought that it was a *bug* that ds/sparse-cone topic does not
match the pattern case insensitively on case insensitive systems,
and from that point of view, letting the earlier part of the topic
graduate without the fix would not make sense, I thought.
Thanks.
next prev parent reply other threads:[~2019-12-13 22:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 19:42 [PATCH 0/1] sparse-checkout: respect core.ignoreCase in cone mode Derrick Stolee via GitGitGadget
2019-12-09 19:43 ` [PATCH 1/1] " Derrick Stolee via GitGitGadget
2019-12-11 18:44 ` Junio C Hamano
2019-12-11 19:11 ` Derrick Stolee
2019-12-11 20:00 ` Junio C Hamano
2019-12-11 20:29 ` Derrick Stolee
2019-12-11 21:37 ` Junio C Hamano
2019-12-12 2:51 ` Derrick Stolee
2019-12-12 20:59 ` Derrick Stolee
2019-12-13 19:05 ` Junio C Hamano
2019-12-13 19:40 ` Derrick Stolee
2019-12-13 22:02 ` Junio C Hamano [this message]
2019-12-13 18:09 ` [PATCH v2 0/1] " Derrick Stolee via GitGitGadget
2019-12-13 18:09 ` [PATCH v2 1/1] " Derrick Stolee via GitGitGadget
2019-12-13 19:58 ` [PATCH v2 0/1] " Junio C Hamano
2019-12-18 11:41 ` [PATCH " Ed Maste
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=xmqqeex7hoj8.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=newren@gmail.com \
--cc=stolee@gmail.com \
--cc=szeder.dev@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.
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).