Re: [PATCH v3 0/8] commit-reach: terminate merge-base walk when one side is exhausted

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 26, 2026, 18:43 UTC
Message-ID: <xmqq1pdt87mb.fsf@gitster.g>
In-Reply-To: <CAL71e4OT0brcmbNXBzKpZuxTh3=R0j+zgxWmV4S-weT3q=vpvQ@mail.gmail.com>

Kristofer Karlsson <krka@spotify.com> writes:

Show 10 quoted lines

> On Fri, 26 Jun 2026 at 18:36, Junio C Hamano <gitster@pobox.com> wrote:
>>
>> I am getting this failure standalone, when applied on the same base
>> as where v2 was applied earlier.  For now I'll eject it from 'seen'.
>>
>
> Yes, I am sorry about that. I submitted it after having missed running t6600
> and accidentally having introduced a bug. I tried to self-report it to avoid
> wasting your time, but I only did so in the relevant v3 patch and
> not this main message.

Ah, I see. Mistakes happen, and do not need to rush, as collaboration is asynchronous around here anyway, and we may read our e-mails in different order ;-)

Thanks. It would have been a more troubling experience if only my set-up were seeing the issue, but I am glad that is not the case.