From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Michael Haggerty <mhagger(at)alum(dot)mit(dot)edu> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Max Bowsher <maxb(at)f2s(dot)com> |
Subject: | Re: git: uh-oh |
Date: | 2010-08-19 09:35:04 |
Message-ID: | AANLkTims9nnkxZKWjVPctO1PNfHvs8+vDhgdTqsdpYct@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Aug 19, 2010 at 07:00, Michael Haggerty <mhagger(at)alum(dot)mit(dot)edu> wrote:
> Magnus Hagander wrote:
>> Is there some way to make cvs2git work this way, and just not bother
>> even trying to create merge commits, or is that fundamentally
>> impossible and we need to look at another tool?
>
> The good news: (I just reminded myself/realized that) Max Bowsher has
> already implemented pretty much exactly what you want in the cvs2svn
> trunk version, including noting in the commit messages any cherry-picks
> that are not reflected in the repo ancestry.
Ah, that's great.
> The bad news: It is broken [1]. But I don't think it should be too much
> work to fix it.
That's less great of course, but it gives hope!
Thanks for your continued efforts!
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2010-08-19 10:45:13 | Re: proposal: tuplestore, tuplesort aggregate functions |
Previous Message | Heikki Linnakangas | 2010-08-19 08:29:19 | PL/pgsSQL EXECUTE USING INTO |