Re: a less-invasive racy-leak fix, was Re: What's cooking in git.git (Dec 2024, #11; Mon, 30)

From: Chris Torek <chris.torek@gmail.com>
Date: Jan 2, 2025, 02:41 UTC
Message-ID: <CAPx1GveQPRop_qJgAQxq+6-2ZsXX6x89sTyTtYFvbMfET09z+g@mail.gmail.com>
In-Reply-To: <20250102023224.GA3853144@coredump.intra.peff.net>

On Wed, Jan 1, 2025 at 6:32 PM Jeff King <peff@peff.net> wrote:

Show 5 quoted lines

> I wonder if revert should have a "squash" mode that reverts all of the
> commits (perhaps in reverse order of application in case they depend on
> each other textually), and then gives you a commit message template
> similar to git-fmt-merge-msg, where we list all of the commits, one per
> line (though probably with their commit ids in this case).

I have kind of wanted this in the past, but never enough to build it, I just did a few separate reverts.

Chris

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