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

On Sun, 19 Jul 2026 at 20:14, Junio C Hamano <[email protected]> wrote:
>
> In any case, we really need to get somebody take a look at these
> patches to move them forward.  Any takers?
>
> Thanks.

Yes it seems we lost some momentum here. I am not personally
stressed about it but it is of course better to reduce the number
of topics in-flight.

If the patch series is getting too large perhaps I need to shrink
it down in size or complexity, but I am not sure if that is wanted
and if so, in which aspect it should be simplified.

Some alternatives:
- Skip the final commit that cleans up the date ordering fallback.
  Currently just a nice win, but it could be submitted separately.
- Skip the extra test helper to get nicer assertion failure
  messages. It was helpful during development but is not strictly
  required.
- Squash together some of the test commits to reduce the number of
  patches.
- Squash together some of the logic changes to jump more directly
  to the desired end state -- though I am not sure if this would
  actually make the review process simpler.

But perhaps this is simply the time of year where people take
more vacation and are thus spending less time on code reviews.

Thanks,
Kristofer