Re: What's cooking in git.git (Sep 2026, #01)

On Wed, Sep 2, 2026 at 6:27 PM Junio C Hamano [off-list ref] wrote:

[...]

* jk/rev-info-argv-to-free (2026-08-31) 2 commits
 - revision: simplify mark_argv_for_free() callers
 - revision: hang on to "freed" argv elements

 The memory ownership of argv elements passed to the revision
 machinery has been made more robust by keeping logically "freed"
 elements alive until the rev_info struct is released, preventing
 use-after-free bugs when options store references to them.

 Will merge to 'next'?
 cf. [ref]
 cf. [ref]
 cf. <xmqq8q5ksvd8.fsf@gitster.g>
 source: [ref]

I think it's good to merge down.

* tc/replay-linearize (2026-08-31) 3 commits
 - replay: offer an option to linearize the commit topology
 - replay: resolve the replay base outside pick_regular_commit()
 - replay: add helper to put entry into replayed_commits

 The 'git replay' command has been taught the '--linearize' option to
 drop merge commits and linearize the replayed history, mimicking 'git
 rebase --no-rebase-merges'.

 Will merge to 'next'?
 cf. [ref]
 source: [ref]

Yes, I think so.

* en/midx-missing-pack-fallback (2026-08-29) 4 commits
 - packfile: recover when a multi-pack-index names a removed pack
 - mktree: do not use OBJECT_INFO_QUICK when checking objects
 - mktree: plug per-tree leak in --batch mode
 - replay: fail gracefully when a merge input is unreadable
 - Merge branch 'ps/odb-generic-corrupt-objects' into en/midx-missing-pack-fallback

 The object lookup machinery has been taught to gracefully recover
 when a multi-pack-index points to an owning pack that was removed
 during a concurrent geometric repack, and 'git replay' has been
 fixed to not segfault when reading such missing objects.

 Will merge to 'next'?
 cf. [ref]
 cf. [ref]
 source: [ref]

I believe so; it was acked by Peff, Patrick, and Stolee.

Stolee and I did add some extra discussion, but not about any changes
to make, but rather clarifications about why the bug occurred
frequently enough to affect production, and more detailed measures of
the cost of the fallback to fix the bug.