From: Tao Klerks <tao@klerks.biz>
Date: Tue, 14 Jun 2022 06:26:50 GMT
Subject: Re: [PATCH] apply: support case-only renames in case-insensitive filesystems
Message-ID: <CAPMMpoi_XgJyEvKvLZ5qk69G_dBs+R0rM359HH90+RY-OGbi-Q@mail.gmail.com>
In-Reply-To: <xmqqo7yw77qo.fsf@gitster.g>

On Mon, Jun 13, 2022 at 8:12 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> Junio C Hamano <gitster@pobox.com> writes:
>
> > And then, you could use --cached (not --index) to bypass the working
> > tree altogether, which is a good way to test the feature without
> > getting affected by the underlying filesystem.  Check both case
> > sensitive and case insensitive cases:
> > ...
> > Likewise, try both sensitive and insensitive one.
>
> As I already wrote tests for basic cases, I'm sending them out,
>
> so that you may extend them with your new cases so that new code you
> write can be checked.
>

Thanks! I'm not sure how to handle this procedurally, especially as
I'm using GitGitGadget, so my patches must always be anchored on a
commit found in the public mirror.

For now I'll add this as a new first commit in my patch, which becomes
my patch series I guess (but keeping your commit metadata
as-specified). Please let me know if there's a better way.