Re: [PATCH v2 05/11] reftable/dump: support dumping a table's block structure

From: Junio C Hamano <gitster@pobox.com>
Date: May 13, 2024, 22:42 UTC
Message-ID: <xmqq34qle3l5.fsf@gitster.g>
In-Reply-To: <ed1c150d909da836a760bc0699f585722d5988e9.1715336798.git.ps@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

Show 7 quoted lines

> We're about to introduce new configs that will allow users to have more
> control over how exactly reftables are written. To verify that these
> configs are effective we will need to take a peak into the actual blocks
> written by the reftable backend.
>
> Introduce a new mode to the dumping logic that prints out the block
> structure. This logic can be invoked via `test-tool dump-reftables -b`.

This step somehow looks familiar. Perhaps that is because I read it more carefully than other steps during the last round.

Looking good to me.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.