Re: [PATCH v6 00/10] commit-reach: terminate merge-base walk when one side is exhausted

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 11, 2026, 20:58 UTC
Message-ID: <xmqqv7al9rbj.fsf@gitster.g>
In-Reply-To: <pull.2149.v6.git.1783776466.gitgitgadget@gmail.com>

"Kristofer Karlsson via GitGitGadget" <gitgitgadget@gmail.com> writes:

Show 6 quoted lines

> Changes since v5:
>
>  * Rebased on next, which now contains kk/commit-reach-find-all-fix. The
>    gen_ordered guard from that topic is carried through patches 7-9 via
>    state.gen_ordered, then removed in patch 10 along with the date-ordering
>    fallback.

As always, do *not* base your patches on 'next'. I cannot apply such a patch series to my tree, as merging the resulting topic down to 'master' will pull _all_ the other topics, including those that are not ready, plus commits that merge these topics into 'next', into 'master'.

Instead, choose the topics that you do depend on, prepare a merge of these branches into a stable base (like v2.55.0 or master), and then build your series on top.

Thanks.