Re: [PATCH RFC v3 18/18] builtin/history: implement "reword" subcommand

From: Patrick Steinhardt <ps@pks.im>
Date: Sep 15, 2025, 09:32 UTC
Message-ID: <aMfdMe72WB3DR4gW@pks.im>
In-Reply-To: <10696a16-3f2b-4844-9f9c-9815976b3e1e@gmail.com>

On Wed, Sep 10, 2025 at 03:05:04PM +0100, Phillip Wood wrote:

Show 7 quoted lines

> On 04/09/2025 15:27, Patrick Steinhardt wrote:
> > Implement a new "reword" subcommand for git-history(1). This subcommand
> > is essentially the same as if a user performed an interactive rebase
> > with a single commit changed to use the "reword" verb.
> 
> The sequencer already knows how to reword a commit, it would be much simpler
> to reuse that code.

I'll drop the second half of this patch series for now to reduce the scope of this series a bit. But once I send the second half I'll have a look at whether this can be simplified.

Patrick

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