Re: What's cooking in git.git (Mar 2024, #01; Mon, 4)

From: Patrick Steinhardt <ps@pks.im>
Date: Mar 5, 2024, 10:19 UTC
Message-ID: <Zebxz1-6FUqQuwmm@tanuki>
In-Reply-To: <xmqq4jdloc9a.fsf@gitster.g>

On Mon, Mar 04, 2024 at 02:36:33PM -0800, Junio C Hamano wrote:

Show 20 quoted lines

> * 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