Re: [PATCH v11 0/8] Introduce git-history(1) command for easy history editing

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 16, 2026, 15:21 UTC
Message-ID: <xmqqy0lxa8i6.fsf@gitster.g>
In-Reply-To: <CABPp-BFbUEGqNAeUtUghLd3oKcZiD88P04AYuTtY4T01F1rzdQ@mail.gmail.com>

Elijah Newren <newren@gmail.com> writes:

Show 13 quoted lines

> On Tue, Jan 13, 2026 at 1:54 AM Patrick Steinhardt <ps@pks.im> wrote:
> [...]
>> Changes in v11:
>>   - Fix overly clever `BUG()` condition.
>>   - Drop the `struct replay_result::merge_conflict` field.
>>   - Return a positive value from `replay_revisions()` in case there was
>>     a conflict.
>>   - Improve a commit message.
>>   - Fix check for whether `setup_revisions_from_strvec()` was
>>     successful.
>>   - Link to v10: https://lore.kernel.org/r/20260112-b4-pks-history-builtin-v10-0-e3c6aa5b4cec@pks.im
>
> This version looks good to merge down.

Thanks.

$ 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.