From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2024, #01; Mon, 4)
Date: Tue, 5 Mar 2024 11:19:59 +0100 [thread overview]
Message-ID: <Zebxz1-6FUqQuwmm@tanuki> (raw)
In-Reply-To: <xmqq4jdloc9a.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
On Mon, Mar 04, 2024 at 02:36:33PM -0800, Junio C Hamano wrote:
> * ps/reftable-iteration-perf-part2 (2024-03-04) 13 commits
> - refs/reftable: precompute prefix length
> - reftable: allow inlining of a few functions
> - reftable/record: decode keys in place
> - reftable/record: reuse refname when copying
> - reftable/record: reuse refname when decoding
> - reftable/merged: avoid duplicate pqueue emptiness check
> - reftable/merged: circumvent pqueue with single subiter
> - reftable/merged: handle subiter cleanup on close only
> - reftable/merged: remove unnecessary null check for subiters
> - reftable/merged: make subiters own their records
> - reftable/merged: advance subiter on subsequent iteration
> - reftable/merged: make `merged_iter` structure private
> - reftable/pq: use `size_t` to track iterator index
>
> The code to iterate over refs with the reftable backend has seen
> some optimization.
>
> Will merge to 'next'?
> source: <cover.1709548907.git.ps@pks.im>
Yeah, I think this topic is ready to go.
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-03-05 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 22:36 What's cooking in git.git (Mar 2024, #01; Mon, 4) Junio C Hamano
2024-03-05 10:19 ` Patrick Steinhardt [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=Zebxz1-6FUqQuwmm@tanuki \
--to=ps@pks.im \
--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