Thread (120 messages) 120 messages, 6 authors, 1d ago

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

From: Junio C Hamano <hidden>
Date: 2026-07-11 20:58:26

"Kristofer Karlsson via GitGitGadget" [off-list ref]
writes:
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help