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, #05; Sat, 11)
Date: Mon, 13 May 2024 09:55:37 +0200 [thread overview]
Message-ID: <ZkHHebHbhGtN0OLr@tanuki> (raw)
In-Reply-To: <ZkGp9TqxO8Y5_kM_@tanuki>
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
On Mon, May 13, 2024 at 07:49:41AM +0200, Patrick Steinhardt wrote:
> On Sat, May 11, 2024 at 04:29:42PM -0700, Junio C Hamano wrote:
[snip]
> > * ps/reftable-write-options (2024-05-10) 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.
> >
> > Will merge to 'next'?
> > source: <cover.1715336797.git.ps@pks.im>
>
> This one is ready from my point of view.
Ah, I only just now read your comments. I think overall this version is
good enough to land, but I also agree with your comments. I'll send a v2
in a bit.
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-05-13 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 23:29 What's cooking in git.git (May 2024, #05; Sat, 11) Junio C Hamano
2024-05-13 5:49 ` Patrick Steinhardt
2024-05-13 7:55 ` Patrick Steinhardt [this message]
2024-05-13 16:34 ` Junio C Hamano
2024-05-15 4:04 ` Patrick Steinhardt
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=ZkHHebHbhGtN0OLr@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).