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

From: D. Ben Knoble <ben.knoble@gmail.com>
Date: Nov 15, 2025, 16:51 UTC
Message-ID: <CALnO6CDCzNbYFC4BGmqC5bhou5rtie7K5OhR_cP1CXJfChim=A@mail.gmail.com>
In-Reply-To: <xmqqcy5kgsjk.fsf@gitster.g>

On Fri, Nov 14, 2025 at 5:27 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 20 quoted lines

>
> * 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>

I've been playing with this for a bit, and have really enjoyed the reword command. I don't have much experience with the split subcommand.

I think I also vaguely recall some discussion about where these things should live?

But otherwise I generally am in favor of the idea and find it useful. I gave an early review of the code but haven't looked closely at the newest version.