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

Re: rebasing a merge

From
Peter Krefting <peter@softwolves.pp.se>
Date
Jun 24, 2010, 09:16 UTC
Message-ID
<alpine.DEB.2.00.1006241012400.28950@ds9.cixit.se>
In-Reply-To
<AANLkTikH9S1GCOwJfmKvO4fTvG46libJtrdMNQeiBm1_@mail.gmail.com>
Jay Soffian:
> I'm familiar with rerere.
Yes, of course, sorry for not recognizing your name :-)
> Which is what I was doing. But it occurred to me that the final tree
> that I want is the same as if I just do a second merge,

So, you want to just discard the change in the new commit on the branch you merged?

You could probably get off by "git cat-file" the commit object, changing the parent reference to point to the newly introduced commit while leaving the rest intact, and then "git hash-object" the new commit object, and then forward the branch head to that one.

-- 
\\// Peter - http://www.softwolves.pp.se/
Previous: Jay SoffianNext: Jay Soffian
Message 5 of 6 in “rebasing a merge”
  1. Jay SoffianJun 17, 2010
  2. Jay SoffianJun 18, 2010
  3. Peter KreftingJun 18, 2010
  4. Jay SoffianJun 18, 2010
  5. Peter KreftingJun 24, 2010
  6. Jay SoffianJun 24, 2010

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.