| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
| 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:15:52 |
| Message-ID: | 4C98DA38.4010706@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09/21/2010 12:07 PM, Aidan Van Dyk wrote:
> But probably the easiest way, if you have a nice clean history, is to
> use "git formatpatch". This produces a nice "series" of patches, with
> your commit message, and content, and dates, all preserved, ready for
> re-applying (git am can do that automatically on the new branch), or
> emailing, or whatever.
Ah. I thought there was something like this but for some reason when I
went looking for it just now I failed to find it.
Thanks for the info. This looks like the best way to go.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhijit Menon-Sen | 2010-09-21 16:21:51 | Re: moving development branch activity to new git repo |
| Previous Message | Elvis Pranskevichus | 2010-09-21 16:15:06 | Re: moving development branch activity to new git repo |