Re: [PATCH 1/1] replay: add --revert option to reverse commit changes

From: Phillip Wood <phillip.wood123@gmail.com>
Date: Nov 27, 2025, 16:21 UTC
Message-ID: <bc974d63-b3f1-4ef9-8fc5-e7e719b6ae89@gmail.com>
In-Reply-To: <38b51e19-7939-4a5e-8ad0-2d8168bc0fac@gmail.com>

Hi Siddharth

On 26/11/2025 19:39, Siddharth Asthana wrote:

Show 8 quoted lines

> 
> The realistic use case is reverting commits from a branch where those 
> commits already exist. For example:
> 
>      git replay --revert main~3..main
> 
> This would revert the last 3 commits on main, creating revert commits on 
> top of main.

We want to be able to revert an arbitary range of commits. That means we need to give --revert a branch name to update in addition to the range of commits to revert. The following example would update "main", reverting all the commits from the branch "feature"

	git replay --revert main main..feature

Thanks

Phillip

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