Re: [PATCH v5 0/4] history: add squash subcommand to fold a range

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 1, 2026, 13:47 UTC
Message-ID: <xmqq8q7urfe1.fsf@gitster.g>
In-Reply-To: <f15456d2-d8b2-4edc-80b4-3a9d8fc77da9@gmail.com>

Phillip Wood <phillip.wood123@gmail.com> writes:

Show 6 quoted lines

> The reason we're introducing the history command is to experiment with 
> providing a better user interface for rewriting history without being 
> bound by the limitations of "git rebase". So I think it would entirely 
> appropriate to try a different format for the squash message here. If it 
> turns out to be a success then we can see if we want to use it in "git 
> rebase" as well.

Do we know concretely things that are bad in the current way "rebase -i" works, so that we can experiment deviation from? If not, the above is going backwards, I'm afraind.

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.