git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (May 2026, #04)

From
Taylor Blau <me@ttaylorr.com>
Date
May 19, 2026, 16:26 UTC
Message-ID
<agyPJa3E2lPI9K/G@nand.local>
In-Reply-To
<xmqqv7clbizy.fsf@gitster.g>
On Mon, May 18, 2026 at 10:32:01AM +0900, Junio C Hamano wrote:
Show 26 quoted lines
> * tb/incremental-midx-part-3.3 (2026-04-29) 16 commits
>  - repack: allow `--write-midx=incremental` without `--geometric`
>  - repack: introduce `--write-midx=incremental`
>  - repack: implement incremental MIDX repacking
>  - packfile: ensure `close_pack_revindex()` frees in-memory revindex
>  - builtin/repack.c: convert `--write-midx` to an `OPT_CALLBACK`
>  - repack-geometry: prepare for incremental MIDX repacking
>  - repack-midx: extract `repack_fill_midx_stdin_packs()`
>  - repack-midx: factor out `repack_prepare_midx_command()`
>  - midx: expose `midx_layer_contains_pack()`
>  - repack: track the ODB source via existing_packs
>  - midx: support custom `--base` for incremental MIDX writes
>  - midx: introduce `--no-write-chain-file` for incremental MIDX writes
>  - midx: use `strvec` for `keep_hashes`
>  - midx: build `keep_hashes` array in order
>  - midx: use `strset` for retained MIDX files
>  - midx-write: handle noop writes when converting incremental chains
>
>  The repacking code has been refactored and compaction of MIDX layers
>  have been implemented, and incremental strategy that does not require
>  all-into-one repacking has been introduced.
>
>  Waiting for response(s) to review comment(s).
>  cf. <agTw579yuy4iHoMq@szeder.dev>
>  cf. <20260513230825.GA1378716@coredump.intra.peff.net>
>  source: <cover.1777507303.git.me@ttaylorr.com>

Apologies, I didn't realize you were waiting on these until seeing this WC report. I sent an extremely tiny reroll

    https://lore.kernel.org/git/cover.1779206239.git.me@ttaylorr.com/

that addresses the two outstanding comments you linked. They are very minor changes, and queueing either version of the series would be equally fine IMHO.

Thanks, Taylor

Previous: Mirko FainaNext: Jeff King
Message 3 of 7 in “What's cooking in git.git (May 2026, #04)”
  1. Junio C HamanoMay 18, 2026
  2. Mirko FainaMay 18, 2026
  3. Taylor BlauMay 19, 2026
  4. Jeff KingMay 19, 2026
  5. Junio C HamanoMay 20, 2026
  6. Justin ToblerMay 19, 2026
  7. Junio C HamanoMay 20, 2026

Read the whole thread, see it on lore, or plain text.

$ 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.