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

Re: flatten-merge history

From
HMHenning Moll <newsscott@gmx.de>
Date
Oct 26, 2014, 14:36 UTC
Message-ID
<544D0702.1050907@gmx.de>
In-Reply-To
<CAP8UFD3jyZ+7bk-xrE=TghzFj9UL=+Mtz-CvFWK9azNrRcOU5Q@mail.gmail.com>
Am 26.10.2014 um 06:46 schrieb Christian Couder:
> Hi,Could you tell us why interactive rebase did not work?

First of all i have to admit that i did not i-rebase-merge, but i-rebase-cherrypick. Now i tried it with i-rebase-merge and it didn't work either. Here's my workflow, which i repeated for all commits of 'extern' (in chronological order'). For simplicity let's assume that there is a parent commit for 'A'

1. For P, A is the nearest prior commit on 'master'
2. on master: git rebase -i A^
3. change A from pick to edit. save. quit
4. git merge P
5. git rebase --continue
 From the perspective of 'master' this worked. But as all of the commits 
have been rewritten, the branches b1 and b2 no longer refer to 'master'. 
Branch b2, for example, still branches off at B and not B'. So after 
this action, my history looks like this:
     P - - - Q - - - - - R       <-extern
       \
A'- m - B'- - - C'- D'- - - E'  <-master
A - - - B - - - C - D
          \           \
           M ...       \         <-b1
                        \
                         W ...   <-b2

A and A' are nearly the same: they only differ in the new GIT_COMITTER_DATE. Now this is what i try to get (after only applying P):

     P - - - Q - - - - - R       <-extern
     \
A'- m - B'- - - C'- D'- - - E'  <-master
          \           \
           M'...       \         <-b1
                        \
                         W'...   <-b2

Regards Henning

Previous: Christian CouderNext: Andreas Schwab
Message 3 of 7 in “flatten-merge history”
  1. Henning MollOct 25, 2014
  2. Christian CouderOct 26, 2014
  3. Henning MollOct 26, 2014
  4. Andreas SchwabOct 26, 2014
  5. Christian CouderOct 26, 2014
  6. Henning MollOct 26, 2014
  7. Andreas SchwabOct 27, 2014

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.