From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Aidan Van Dyk <aidan@highrise.ca>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Markus Wanner <markus@bluegap.ch>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: Wed, 27 May 2009 17:59:47 +0300
Message-ID: <4A1D5563.1000001@enterprisedb.com> (raw)
In-Reply-To: <20090527140329.GL15213@yugib.highrise.ca>
References: <4A1A52F5.7030009@hagander.net>
<20090525122821.GO8123@tamriel.snowman.net>
<4A1BABBC.7070803@hagander.net>
<4A1BE039.70008@dunslane.net>
<10273.1243343651@sss.pgh.pa.us>
<4A1BFF70.4000506@dunslane.net>
<20090526144812.GC15213@yugib.highrise.ca>
<20090527121532.83276r2btyqp716s@mail.bluegap.ch>
<4A1D1E64.6030908@hagander.net>
<4A1D2290.7060907@enterprisedb.com>
<20090527140329.GL15213@yugib.highrise.ca>
Aidan Van Dyk wrote:
> * Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> [090527 07:29]:
>
>> OTOH, there's some value in staying with current GIT repository. In
>> EnterpriseDB, we maintain all the Oracle-compatibility stuff in a GIT
>> repository that's based on the PostgreSQL mirror. If PostgreSQL switches
>> to a new GIT repository/mirror, I'll have to rebase all that, and I'm
>> not sure how well that works with all the merges and stuff. I'm probably
>> the one with most complex situation, but others who have
>> work-in-progress patches in local repositories will face the same issue
>> at a smaller scale.
>
> But there are oodles of options in git available to handle a cutover
> like that:
> - grafts
> - filter-branch
Okay, your git-fu is stronger than mine, I had never heard of grafts
before :-).
> - rebase (the new rebase toolset can even attempt to rebase a DAG onto an
> existing DAG, not just linear patches))
That's interesting, I once tested git-rebase on the version I have
installed on a similar scenario and it didn't handle merges. If it does
now, that's great.
> But, if there is nothing wrong with the current repo (except that it
> doesn't have tags), than we can easily add tags to it...
Yep. There's not *that* many tags in the CVS repository, we could just
add them manually.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: heikki.linnakangas@enterprisedb.com, aidan@highrise.ca, magnus@hagander.net, markus@bluegap.ch, andrew@dunslane.net
Subject: Re: PostgreSQL Developer meeting minutes up
In-Reply-To: <4A1D5563.1000001@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox