Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 4720C63560E for ; Tue, 2 Jun 2009 13:27:20 -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 75165-01-3 for ; Tue, 2 Jun 2009 13:27:17 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp103.biz.mail.mud.yahoo.com (smtp103.biz.mail.mud.yahoo.com [68.142.200.238]) by mail.postgresql.org (Postfix) with SMTP id BAE166352E4 for ; Tue, 2 Jun 2009 13:27:07 -0300 (ADT) Received: (qmail 26428 invoked from network); 2 Jun 2009 16:27:06 -0000 Received: from unknown (HELO ?192.168.5.110?) (rm_pg@75.36.180.107 with plain) by smtp103.biz.mail.mud.yahoo.com with SMTP; 2 Jun 2009 16:27:06 -0000 X-Yahoo-SMTP: acjdBE2swBAAX9ja0RY4hQi0ggqg.Ml3.omUEQJ1xZsuGIb6CRE- X-YMail-OSG: bpCz2L0VM1keVlO5Ho_gSVGGpBDvVsKe3cZ1Dn1i4bS6JqvWcqsYXAq9.EylvOhfdGdDucl5diFjdFTjXYGYlOKHH_LhMgOP1jqr2Q2Wxz60pxHyFM9UnyhdN5cNe.tWSGONcaKHMxD5O4X2wWqQjcojb_gdifdrhYiYwfU7l67QDMAnAbBmobp_h0WmbP8gC5CPaIFcyNQM_FZOx4G4mAqGHs3Q1xkT9muLbgl2Wx7H0wSTc_hL6.O6p4u9ZglPeN1qpTziCpOwe5KyfRzLfePU1pw5qdvjcm7IYGNQwyZ8LOFKTLBCuYhzwZLpMYCOs4BRz16QZ7QTJ2hmOENEGxIHKk8tmaOeIBdPxDVF4v9mAYBb3o.sQ60Nww-- X-Yahoo-Newman-Property: ymail-3 Message-ID: <4A2552D6.101@cheapcomplexdevices.com> Date: Tue, 02 Jun 2009 09:27:02 -0700 From: Ron Mayer User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: Aidan Van Dyk CC: Markus Wanner , Marko Kreen , Heikki Linnakangas , Magnus Hagander , Andrew Dunstan , PostgreSQL-development Subject: Re: PostgreSQL Developer meeting minutes up References: <20090529170559.99155w414h94hazb@mail.bluegap.ch> <20090529151228.GZ15213@yugib.highrise.ca> <20090529171818.89937lf3o1oyzfsq@mail.bluegap.ch> <20090529153435.GA15213@yugib.highrise.ca> <4A241340.9080903@bluegap.ch> <20090602134831.186767ksvmsgj8gf@mail.bluegap.ch> <20090602162333.369974jcc3jpn3dx@mail.bluegap.ch> <20090602145000.GE23972@yugib.highrise.ca> In-Reply-To: <20090602145000.GE23972@yugib.highrise.ca> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200906/178 X-Sequence-Number: 139233 Aidan Van Dyk wrote: > * Markus Wanner [090602 10:23]: >> As mentioned before, I'd personally favor *all* of the back-ports to >> actually be merges of some sort, because that's what they effectively >> are. However, that also bring up the question of how we are going to do >> back-patches in the future with git. > > Well, if people get comfortable with it, I expect that "backports" don't > happenen.. Bugs are fixed where they happen, and "merged" forward into > all affected "later development" based on the bugged area. I imagine the closest thing to existing practices would be that people would to use "git-cherry-pick -x -n" to backport only the commits they wanted from the current branch into the back branches. AFAICT, this doesn't record a merge in the GIT history, but looks a lot like the linear history from CVS - with the exception that the comment added by "-x" explicitly refers to the exact commit from the main branch.