From: "René Scharfe" <l.s.r@web.de>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2025, #05; Thu, 17)
Date: Fri, 18 Jul 2025 10:55:10 +0200 [thread overview]
Message-ID: <d0e9826d-a972-47ca-ab69-f1711efa4a74@web.de> (raw)
In-Reply-To: <xmqqo6ti49fk.fsf@gitster.g>
On 7/18/25 2:41 AM, Junio C Hamano wrote:
> * 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é
prev parent reply other threads:[~2025-07-18 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 0:41 What's cooking in git.git (Jul 2025, #05; Thu, 17) Junio C Hamano
2025-07-18 8:55 ` René Scharfe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d0e9826d-a972-47ca-ab69-f1711efa4a74@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).