From: Elijah Newren Date: Fri, 16 Jan 2026 07:00:59 GMT Subject: Re: What's cooking in git.git (Jan 2026, #05) Message-ID: In-Reply-To: On Thu, Jan 15, 2026 at 10:59 AM Junio C Hamano wrote: > * ac/sparse-checkout-string-list-cleanup (2026-01-15) 1 commit > - sparse-checkout: optimize string_list construction > > Code clean-up. > > Will merge to 'next'. > source: <20260115130935.93526-1-amishhhaaaa@gmail.com> Shouldn't it restore the string_list_remove_duplicates() calls first? (See 20260115200903.GB1053259@coredump.intra.peff.net and fc14e0e5-93bc-4805-a20d-d2aa4eb87ddb@web.de ) > * pw/replay-drop-empty (2025-12-18) 2 commits > - replay: drop commits that become empty > - Merge branch 'ps/history' into pw/replay-drop-empty > (this branch uses ps/history.) > > "git replay" is taught to drop commits that become empty (not the > ones that are empty in the original). > > On hold, until the base topic gains consensus and stabilizes. > source: <375adc4e941f3bb22a2b12ee26a083951ed724dd.1766076625.git.phillip.wood@dunelm.org.uk> I think the base topic has done so now (as I'll note below), so this should be ready to advance. > * ps/history (2026-01-13) 9 commits > - builtin/history: implement "reword" subcommand > - builtin: add new "history" command > - wt-status: provide function to expose status for trees > - replay: support updating detached HEAD > - replay: support empty commit ranges > - replay: small set of cleanups > - builtin/replay: move core logic into "libgit.a" > - builtin/replay: extract core logic to replay revisions > - Merge branch 'kh/replay-invalid-onto-advance' into ps/history > (this branch is used by pw/replay-drop-empty.) > > "git history" history rewriting UI. > > Will merge to 'next'? > source: <20260113-b4-pks-history-builtin-v11-0-e74ebfa2652d@pks.im> Yes, I think it's ready.