All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian MICHON" <christian.michon@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: "Andreas Ericsson" <ae@op5.se>, "Git Mailing List" <git@vger.kernel.org>
Subject: Re: More help needed on merging unrelated repos
Date: Thu, 6 Nov 2008 13:13:42 +0100	[thread overview]
Message-ID: <46d6db660811060413q7f4e2437maa6d87a27b8704b@mail.gmail.com> (raw)
In-Reply-To: <20081106083751.GA10359@diana.vm.bytemark.co.uk>

On Thu, Nov 6, 2008 at 9:37 AM, Karl Hasselström <kha@treskal.com> wrote:
> 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
>

nice suggestion Karl! it took a while to understand all the
consequences and workflow.
On top of your suggestion, I had to remove the
refs/original/refs/heads/master and the grafts file.

It worked well: quite a spell, but an efficient one. Kudo++

-- 
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !

  reply	other threads:[~2008-11-06 12:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 13:14 More help needed on merging unrelated repos Christian MICHON
2008-11-04 20:12 ` Andreas Ericsson
2008-11-04 21:08   ` Christian MICHON
2008-11-04 22:04     ` Andreas Ericsson
2008-11-04 22:30       ` Christian MICHON
2008-11-06  8:37         ` Karl Hasselström
2008-11-06 12:13           ` Christian MICHON [this message]
2008-11-06 15:28             ` Karl Hasselström

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46d6db660811060413q7f4e2437maa6d87a27b8704b@mail.gmail.com \
    --to=christian.michon@gmail.com \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=kha@treskal.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.