git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Odd merge behaviour involving reverts

From
Linus Torvalds <torvalds@linux-foundation.org>
Date
Dec 19, 2008, 04:23 UTC
Message-ID
<alpine.LFD.2.00.0812182022170.14014@localhost.localdomain>
In-Reply-To
<76718490812182018x37e3d6fob8d817c0e0b0e293@mail.gmail.com>
On Thu, 18 Dec 2008, Jay Soffian wrote:
> 
> Instead of reverting the revert, why not rebase the branch which was
> merged to the point after the revert was done?

Sure, you can do that too. However, that has its own set of problems, ie all the "ok, who else was working based on this branch" thing.

But no, there are no single right answers. Rebasing may well be a reasonable approach.

		Linus
Previous: Jay SoffianNext: Daniel Barkalow
Message 10 of 17 in “Odd merge behaviour involving reverts”
  1. AlanDec 18, 2008
  2. Linus TorvaldsDec 18, 2008
  3. AlanDec 19, 2008
  4. Linus TorvaldsDec 19, 2008
  5. AlanDec 19, 2008
  6. Linus TorvaldsDec 19, 2008
  7. Nanako ShiraishiDec 19, 2008
  8. Linus TorvaldsDec 19, 2008
  9. Jay SoffianDec 19, 2008
  10. Linus TorvaldsDec 19, 2008
  11. Daniel BarkalowDec 19, 2008
  12. Junio C HamanoDec 19, 2008
  13. Nanako ShiraishiDec 19, 2008
  14. Junio C HamanoDec 19, 2008
  15. Nanako ShiraishiDec 19, 2008
  16. Junio C HamanoDec 19, 2008
  17. Boyd Stephen Smith Jr.Dec 19, 2008

Read the whole thread, see it on lore, or plain text.

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