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

From: Kristofer Karlsson <krka@spotify.com>
Date: Jun 26, 2026, 16:43 UTC
Message-ID: <CAL71e4OT0brcmbNXBzKpZuxTh3=R0j+zgxWmV4S-weT3q=vpvQ@mail.gmail.com>
In-Reply-To: <xmqqjyrl8di0.fsf@gitster.g>

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.

I will be more careful for v4 (and onwards)

Thanks, Kristofer

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.