Re: moving development branch activity to new git repo - Mailing list pgsql-hackers

From Abhijit Menon-Sen
Subject Re: moving development branch activity to new git repo
Date
Msg-id 20100921162151.GA734@toroid.org
Whole thread Raw
In response to Re: moving development branch activity to new git repo  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
At 2010-09-21 11:59:09 -0400, andrew@dunslane.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


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: moving development branch activity to new git repo
Next
From: Abhijit Menon-Sen
Date:
Subject: Re: .gitignore files, take two