Re: What's cooking in git.git (Nov 2025, #04; Fri, 14)

From: Phillip Wood <phillip.wood123@gmail.com>
Date: Nov 17, 2025, 16:31 UTC
Message-ID: <a407a793-9636-42ea-afe8-1283b1e220b7@gmail.com>
In-Reply-To: <CALnO6CDCzNbYFC4BGmqC5bhou5rtie7K5OhR_cP1CXJfChim=A@mail.gmail.com>

On 15/11/2025 16:51, D. Ben Knoble wrote:

Show 23 quoted lines

> On Fri, Nov 14, 2025 at 5:27 PM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> * ps/history (2025-10-27) 12 commits
>>   - builtin/history: implement "split" subcommand
>>   - cache-tree: allow writing in-memory index as tree
>>   - add-patch: add support for in-memory index patching
>>   - add-patch: remove dependency on "add-interactive" subsystem
>>   - add-patch: split out `struct interactive_options`
>>   - add-patch: split out header from "add-interactive.h"
>>   - builtin/history: implement "reword" subcommand
>>   - builtin: add new "history" command
>>   - replay: stop using `the_repository`
>>   - replay: extract logic to pick commits
>>   - wt-status: provide function to expose status for trees
>>   - Merge branch 'sa/replay-atomic-ref-updates' into ps/history
>>   (this branch uses sa/replay-atomic-ref-updates.)
>>
>>   "git history" history rewriting UI.
>>
>>   Comments?
>>   source: <20251027-b4-pks-history-builtin-v6-0-407dd3f57ad3@pks.im>
> 
> But otherwise I generally am in favor of the idea and find it useful.

I agree with this and I'm pleased it is reusing some of the internals of "git replay" now. I've just reviewed the first half, I'll try and do the rest sometime this week.

Thanks

Phillip