Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 005CD632A7E for ; Wed, 27 May 2009 11:59:54 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 57727-10 for ; Wed, 27 May 2009 11:59:53 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by mail.postgresql.org (Postfix) with SMTP id A0450632957 for ; Wed, 27 May 2009 11:59:52 -0300 (ADT) Received: from source ([74.125.78.27]) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKSh1VZ+2QpHVFp+K91eIEXWhdWtS6WoTD@postini.com; Wed, 27 May 2009 07:59:53 PDT Received: by ey-out-2122.google.com with SMTP id d26so958052eyd.27 for ; Wed, 27 May 2009 07:59:50 -0700 (PDT) Received: by 10.210.17.14 with SMTP id 14mr42460ebq.56.1243436390846; Wed, 27 May 2009 07:59:50 -0700 (PDT) Received: from ?80.223.212.7? (dsl-hkibrasgw2-fed4df00-7.dhcp.inet.fi [80.223.212.7]) by mx.google.com with ESMTPS id 10sm646889eyd.52.2009.05.27.07.59.49 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 27 May 2009 07:59:49 -0700 (PDT) Message-ID: <4A1D5563.1000001@enterprisedb.com> Date: Wed, 27 May 2009 17:59:47 +0300 From: Heikki Linnakangas Organization: EnterpriseDB User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Aidan Van Dyk CC: Magnus Hagander , Markus Wanner , Andrew Dunstan , PostgreSQL-development Subject: Re: PostgreSQL Developer meeting minutes up 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> In-Reply-To: <20090527140329.GL15213@yugib.highrise.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200905/1114 X-Sequence-Number: 138656 Aidan Van Dyk wrote: > * Heikki Linnakangas [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