Re: [RFC] Second parent for reverts

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: May 9, 2007, 20:07 UTC
Message-ID: <Pine.LNX.4.64.0705092206540.4167@racer.site>
In-Reply-To: <Pine.LNX.4.64.0705091406350.18541@iabervon.org>

Hi,

On Wed, 9 May 2007, Daniel Barkalow wrote:

Show 5 quoted lines

> The discussion about having a header to specify, for a revert commit, 
> what it reverts made me realize that this header *would* be useful, but 
> that we don't need a *new* header for it. I think that the right method 
> is to add the parent of the reverted commit as a second parent for the 
> revert.

I am not so sure. In a sense, you are correct. But everybody who does "git log --no-merges" would no longer see reverts. Which is somewhat incorrect.

Ciao, Dscho

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