From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2024, #05; Fri, 12)
Date: Mon, 15 Apr 2024 10:37:25 -0700 [thread overview]
Message-ID: <xmqqpluqo7ca.fsf@gitster.g> (raw)
In-Reply-To: <ZhzV38Ga1Lg99bUF@tanuki> (Patrick Steinhardt's message of "Mon, 15 Apr 2024 09:23:11 +0200")
Patrick Steinhardt <ps@pks.im> writes:
>> * ps/reftable-block-iteration-optim (2024-03-27) 9 commits
>> - reftable/block: reuse `zstream` state on inflation
>> - reftable/block: open-code call to `uncompress2()`
>> - reftable/block: reuse uncompressed blocks
>> - reftable/reader: iterate to next block in place
>> - reftable/block: move ownership of block reader into `struct table_iter`
>> - reftable/block: introduce `block_reader_release()`
>> - reftable/block: better grouping of functions
>> - reftable/block: merge `block_iter_seek()` and `block_reader_seek()`
>> - reftable/block: rename `block_reader_start()`
>>
>> The code to iterate over reftable blocks has seen some optimization
>> to reduce memory allocation and deallocation.
>>
>> Needs review.
>> source: <cover.1711519925.git.ps@pks.im>
The above refers to v1; as ps/reftable-binsearch-updates, which v2
added as its dependency, has been merged to 'master', let me pick
that one up.
Thanks.
next prev parent reply other threads:[~2024-04-15 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 1:36 What's cooking in git.git (Apr 2024, #05; Fri, 12) Junio C Hamano
2024-04-15 7:23 ` Patrick Steinhardt
2024-04-15 17:37 ` Junio C Hamano [this message]
2024-04-16 0:48 ` brian m. carlson
2024-04-16 8:26 ` Junio C Hamano
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=xmqqpluqo7ca.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).