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

Re: More help needed on merging unrelated repos

From
Karl Hasselström <kha@treskal.com>
Date
Nov 6, 2008, 08:37 UTC
Message-ID
<20081106083751.GA10359@diana.vm.bytemark.co.uk>
In-Reply-To
<46d6db660811041430l74d9a100kc15ac46dea8ff63f@mail.gmail.com>
On 2008-11-04 23:30:56 +0100, Christian MICHON wrote:
> note the merge can work, but it's still done in 2 steps. :(
> thanks for suggesting this.

If it had worked, you'd have gotten just one merge commit. What you want to do is entirely possible, but it seems the high-level commands were not designed with your use-case in mind.

Another thing you could try is to merge the two branches separately, getting a history like this:

  p1----\
         \
  p2---A--B
      /
  p3--

And then use grafts to convince git that B has parents p1, p2, and p3 (instead of its actual parents p1 and A). (Grep for "graft" in the Documentation directory.)

And then use git-filter-branch to rewrite history so that the grafted history becomes the real history.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Christian MICHONNext: Christian MICHON
Message 6 of 8 in “More help needed on merging unrelated repos”
  1. Christian MICHONNov 4, 2008
  2. Andreas EricssonNov 4, 2008
  3. Christian MICHONNov 4, 2008
  4. Andreas EricssonNov 4, 2008
  5. Christian MICHONNov 4, 2008
  6. Karl HasselströmNov 6, 2008
  7. Christian MICHONNov 6, 2008
  8. Karl HasselströmNov 6, 2008

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.