Re: moving development branch activity to new git repo

From: Abhijit Menon-Sen <ams(at)toroid(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: moving development branch activity to new git repo
Date: 2010-09-21 16:21:51
Message-ID: 20100921162151.GA734@toroid.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 2010-09-21 11:59:09 -0400, andrew(at)dunslane(dot)net wrote:
>
> However, that does mean losing the private commit history. I'm not
> sure much can be done about that, unless you migrate each commit
> separately, which could be painful.

It doesn't have to be painful.

Determine what patches from the old repository you want to apply, and
create a branch in the newly-cloned repository to apply them to. Then
use (cd ../oldrepo;git format-patch -k --stdout R1..R2)|git am -3 -k"
to apply a series of patches (between revisions R1 and R2; adjust as
needed) to your branch (i.e. when you have it checked out).

See git-format-patch(1) and git-am(1) for more details (or feel free
to ask if you need more help).

-- ams

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Abhijit Menon-Sen 2010-09-21 16:26:56 Re: .gitignore files, take two
Previous Message Andrew Dunstan 2010-09-21 16:15:52 Re: moving development branch activity to new git repo