From: Patrick Steinhardt <ps@pks.im>
Date: Tue, 18 Nov 2025 09:58:58 GMT
Subject: Re: What's cooking in git.git (Nov 2025, #04; Fri, 14)
Message-ID: <aRxDYkeAi8T-HH8M@pks.im>
In-Reply-To: <a407a793-9636-42ea-afe8-1283b1e220b7@gmail.com>

On Mon, Nov 17, 2025 at 04:31:00PM +0000, Phillip Wood wrote:
> On 15/11/2025 16:51, D. Ben Knoble wrote:
> > 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.

Perfect, thanks! I won't be able to address the feedback this or next
week, but will do it once I'm back in office.

Patrick