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

Re: rewrite history

From
Jeff King <peff@peff.net>
Date
Jun 16, 2011, 19:26 UTC
Message-ID
<20110616192644.GB13466@sigill.intra.peff.net>
In-Reply-To
<362053118.20110616231758@gmail.com>
On Thu, Jun 16, 2011 at 11:17:58PM +0400, Ilya Basin wrote:
Show 10 quoted lines
> Hi list. There were 2 branches. One's HEAD was modified to match a
> specific commit at another branch. Now, how to merge them according to
> this scheme?
> 
> A---B---X---E---F
>                      =>  C---D---X---E---F
> C---D---X'
> 
> X and X' have no difference. I tried to write a script to cherry-pick
> E and F, but some of commits are merges and cherry-pick fails.

I think you just want to rebase using the "-p" option to preserve merges. Something like:

  $ git checkout -b rebased-branch F
  $ git rebase -p --onto D B

that will pick X, E, and F, and replay them on top of D, resulting in the graph you showed above. You could also do:

  $ git rebase -p --onto X' X
if you wanted to keep X' instead of X.

The new history will be stored on "rebased-branch". You can make sure it looks good to you, and then:

  $ git branch -f my_original_branch rebased-branch

to move the state over to your original branch. You could also just do the rebase directly on the original A-B-X-E-F branch.

-Peff
Previous: Ilya BasinNext: Junio C Hamano
Message 2 of 9 in “rewrite history”
  1. Ilya BasinJun 16, 2011
  2. Jeff KingJun 16, 2011
  3. Junio C HamanoJun 16, 2011
  4. Jeff KingJun 16, 2011
  5. Re[2]: rewrite historyIlya Basin, Jun 16, 2011
  6. Jeff KingJun 16, 2011
  7. Re[2]: rewrite historyIlya Basin, Jun 16, 2011
  8. Re[3]: rewrite historyIlya Basin, Jun 16, 2011
  9. Marc BranchaudJun 16, 2011

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.