Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 9A8D5633CCD for ; Wed, 27 May 2009 11:03:42 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 82153-05-3 for ; Wed, 27 May 2009 11:03:30 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from oak.highrise.ca (oak.highrise.ca [70.38.99.169]) by mail.postgresql.org (Postfix) with ESMTP id 8ECFE634D2B for ; Wed, 27 May 2009 11:03:31 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by oak.highrise.ca (Postfix) with ESMTP id 109F4AC428; Wed, 27 May 2009 10:03:30 -0400 (EDT) Date: Wed, 27 May 2009 10:03:30 -0400 From: Aidan Van Dyk To: Heikki Linnakangas Cc: Magnus Hagander , Markus Wanner , Andrew Dunstan , PostgreSQL-development Subject: Re: PostgreSQL Developer meeting minutes up Message-ID: <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> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nrM5Z5VIJgwP9LWp" Content-Disposition: inline In-Reply-To: <4A1D2290.7060907@enterprisedb.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=AWL=0.000 X-Spam-Level: X-Archive-Number: 200905/1111 X-Sequence-Number: 138653 --nrM5Z5VIJgwP9LWp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline * 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 - rebase (the new rebase toolset can even attempt to rebase a DAG onto an existing DAG, not just linear patches)) So I'm whatever becomes the "official" git repo can simply be "grafted" into your history, your your new development grafted on to the "official" history... 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... a. -- Aidan Van Dyk Create like a god, aidan@highrise.ca command like a king, http://www.highrise.ca/ work like a slave. --nrM5Z5VIJgwP9LWp Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFKHUgxuVxNPsxNPScRAr1DAJ9zxUatCrdEO5t6OmkZ62Ee7dqtXACgtSXL Jl6Hu2pk6vCqgro0RWwpgEo= =S41h -----END PGP SIGNATURE----- --nrM5Z5VIJgwP9LWp--