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

Re: flatten-merge history

From
Christian Couder <christian.couder@gmail.com>
Date
Oct 26, 2014, 05:46 UTC
Message-ID
<CAP8UFD3jyZ+7bk-xrE=TghzFj9UL=+Mtz-CvFWK9azNrRcOU5Q@mail.gmail.com>
In-Reply-To
<544B9839.7000302@gmx.de>
Hi,
On Sat, Oct 25, 2014 at 2:31 PM, Henning Moll <newsScott@gmx.de> wrote:
Show 31 quoted lines
> Hi,
>
> suppose the following history
>
>     P - - - Q - - - - - R       <-extern
>
> A -- - B - - - C - D - - - E   <-master
>           \           \
>           M ...       \         <-b1
>                           \
>                           W ...   <-b2
>
>
> Note that master and extern do not have a common parent. Both histories are
> 'distinct', they do not share common files, so there can't be any merge
> conflicts. What i want to achieve is this history:
>
>     P - - - Q - - - - - R       <-extern
>
> A -P'- B'- Q'- C'- D'- R'- E'  <-master
>             \           \
>             M'...       \         <-b1
>                             \
>                             W'...   <-b2
>
> The two histories should be merged in chronological order.
> So while master reflects P-Q-R, b2 should only reflect P-Q and b1 should
> only reflect P.
>
> All my current attempts (surgery with git replace or interactive rebase
> combined with merging) were not successfull.

Could you tell us why interactive rebase did not work? If there can't be any merge conflict between both histories, it should have worked without asking you to resolve any conflict.

Best, Christian.

Previous: Henning MollNext: Henning Moll
Message 2 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.