From: Phillip Wood <phillip.wood123@gmail•com>
To: "D. Ben Knoble" <ben.knoble@gmail•com>,
Junio C Hamano <gitster@pobox•com>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Nov 2025, #04; Fri, 14)
Date: Mon, 17 Nov 2025 16:31:00 +0000 [thread overview]
Message-ID: <a407a793-9636-42ea-afe8-1283b1e220b7@gmail.com> (raw)
In-Reply-To: <CALnO6CDCzNbYFC4BGmqC5bhou5rtie7K5OhR_cP1CXJfChim=A@mail.gmail.com>
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.
Thanks
Phillip
next prev parent reply other threads:[~2025-11-17 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 22:26 What's cooking in git.git (Nov 2025, #04; Fri, 14) Junio C Hamano
2025-11-15 16:51 ` D. Ben Knoble
2025-11-17 16:31 ` Phillip Wood [this message]
2025-11-17 22:48 ` Junio C Hamano
2025-11-18 9:58 ` Patrick Steinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a407a793-9636-42ea-afe8-1283b1e220b7@gmail.com \
--to=phillip.wood123@gmail$(echo .)com \
--cc=ben.knoble@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=phillip.wood@dunelm$(echo .)org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox