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

rebaseing topic branch which has merges from master

From
MMMarc Mutz <marc@kdab.net>
Date
Apr 14, 2009, 15:03 UTC
Message-ID
<gs28e1$ktn$1@ger.gmane.org>
Hi,
I'd like to achieve the following:
---(BP)--- ....---(M1)---     ...    ---(M2)---   .... master
     \              \                     \
      \              \                     \
      (T1)---(T2)---(T3)---(T4)---(T5)---(T6)--- .... topic
 
 
                                   ||
                                   ||
                                   VV
 
 
---(BP)---....---(M1)---     ...    ---(M2)---   .... master
                   \                     \_____________
                    \                                  \
                   (T1)---(T2)---(T3)---(T4)---(T5)---(T6)--- .... topic
However, when I run
  git checkout topic
  git rebase M1
I get a conflict somewhere around a merge commit down the road, and when I
gitk to check where I am, I see master commits (M2, M2^) that have changed
their (sha1) name. That shouldn't happen, afaiu git, so what's wrong? Is
this simply not supported? Can I flatten the merge commits somehow before
rebasing?

Thanks, Marc

Message 1 of 1 in “rebaseing topic branch which has merges from master”
  1. Marc MutzApr 14, 2009

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.