git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 17, 2025, 22:48 UTC
Message-ID
<xmqqo6p0gtrx.fsf@gitster.g>
In-Reply-To
<a407a793-9636-42ea-afe8-1283b1e220b7@gmail.com>
Phillip Wood <phillip.wood123@gmail.com> writes:
Show 28 quoted lines
> 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!
Previous: Phillip WoodNext: Patrick Steinhardt
Message 4 of 5 in “What's cooking in git.git (Nov 2025, #04; Fri, 14)”
  1. Junio C HamanoNov 14, 2025
  2. D. Ben KnobleNov 15, 2025
  3. Phillip WoodNov 17, 2025
  4. Junio C HamanoNov 17, 2025
  5. Patrick SteinhardtNov 18, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.