Re: What's cooking in git.git (Jul 2025, #05; Thu, 17)

From: René Scharfe <l.s.r@web.de>
Date: Jul 18, 2025, 08:55 UTC
Message-ID: <d0e9826d-a972-47ca-ab69-f1711efa4a74@web.de>
In-Reply-To: <xmqqo6ti49fk.fsf@gitster.g>

On 7/18/25 2:41 AM, Junio C Hamano wrote:

Show 12 quoted lines

> * rs/pop-recent-commit-with-prio-queue (2025-07-16) 4 commits
>  - fixup! commit: convert pop_most_recent_commit() to prio_queue
>  - commit: use prio_queue_replace() in pop_most_recent_commit()
>  - prio-queue: add prio_queue_replace()
>  - commit: convert pop_most_recent_commit() to prio_queue
> 
>  The pop_most_recent_commit() function can have quite expensive
>  worst case performance characteristics, which has been optimized by
>  using prio-queue data structure.
> 
>  Will merge to 'next', after squashing the fixup in?
>  source: <bc079b3c-a472-4f5d-95ca-390f9de25196@web.de>

Will send v2 shortly to address the feedback so far. Pondering whether to make the replace optimization implicit (no longer requiring prio_queue_replace()), but that's probably worth a new series.

René