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 (May 2024, #04; Thu, 9)
Date: Fri, 10 May 2024 09:54:25 +0200 [thread overview]
Message-ID: <Zj3SsbHLp-gH_Jey@tanuki> (raw)
In-Reply-To: <xmqqfruqsjb6.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
On Thu, May 09, 2024 at 03:37:49PM -0700, Junio C Hamano wrote:
> * ps/reftable-write-options (2024-05-03) 11 commits
> - refs/reftable: allow configuring geometric factor
> - reftable: make the compaction factor configurable
> - refs/reftable: allow disabling writing the object index
> - refs/reftable: allow configuring restart interval
> - reftable: use `uint16_t` to track restart interval
> - refs/reftable: allow configuring block size
> - reftable/dump: support dumping a table's block structure
> - reftable/writer: improve error when passed an invalid block size
> - reftable/writer: drop static variable used to initialize strbuf
> - reftable: consistently pass write opts as value
> - reftable: consistently refer to `reftable_write_options` as `opts`
>
> The knobs to tweak how reftable files are written have been made
> available as configuration variables.
>
> Needs review.
> source: <cover.1714630191.git.ps@pks.im>
Just in case you missed it, there was a review by Justin already [1].
It's okay if you want to wait for more reviews though.
Patrick
[1]: https://lore.kernel.org/git/2rozmhwf2jpyqmy5vtf2t664ko7ztinbzdmwirrqxspjwzgj7t@jctxour2o73r/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-05-10 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 22:37 What's cooking in git.git (May 2024, #04; Thu, 9) Junio C Hamano
2024-05-10 1:04 ` Junio C Hamano
2024-05-10 6:32 ` Torsten Bögershausen
2024-05-10 7:54 ` Patrick Steinhardt [this message]
2024-05-10 15:35 ` Junio C Hamano
2024-05-10 16:19 ` Patrick Steinhardt
2024-05-10 18:39 ` Justin Tobler
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=Zj3SsbHLp-gH_Jey@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.