Received: from maia.hub.org (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 647E26329A2
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Sat,  6 Jun 2009 17:30:29 -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 32780-07
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Sat,  6 Jun 2009 17:30:28 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from shaykin.bluegap.ch (shaykin.bluegap.ch [78.46.81.73])
	by mail.postgresql.org (Postfix) with ESMTP id 5A8306336D0
	for <pgsql-hackers@postgresql.org>;
	Sat,  6 Jun 2009 17:30:28 -0300 (ADT)
Received: from [192.168.2.103] (p549768E7.dip.t-dialin.net
	[::ffff:84.151.104.231]) (AUTH: CRAM-MD5 markus@bluegap.ch)
	by shaykin.bluegap.ch with esmtp; Sat, 06 Jun 2009 22:30:25 +0200
	id 000000000255C021.000000004A2AD1E1.00003383
Message-ID: <4A2AD1E0.1020901@bluegap.ch>
Date: Sat, 06 Jun 2009 22:30:24 +0200
From: Markus Wanner <markus@bluegap.ch>
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Andrew Dunstan <andrew@dunslane.net>,
	Ron Mayer <rm_pg@cheapcomplexdevices.com>,
	Marko Kreen <markokr@gmail.com>, Greg Stark <stark@enterprisedb.com>,
	Andres Freund <andres@anarazel.de>, Aidan Van Dyk <aidan@highrise.ca>,
	Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>,
	Magnus Hagander <magnus@hagander.net>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL Developer meeting minutes up
References: <20090526144812.GC15213@yugib.highrise.ca>
	<e51f66da0906020546l578e56c8m52f5a6e10760eaf9@mail.gmail.com>
	<20090602162333.369974jcc3jpn3dx@mail.bluegap.ch>
	<e51f66da0906020834q7e6e3401jf77f40f9924bbace@mail.gmail.com>
	<20090602180702.15986cp384yo3l7q@mail.bluegap.ch>
	<e51f66da0906020917m274debd5u3288d6d56b62daf7@mail.gmail.com>
	<20090603131004.12934iyrr4f7rlsc@mail.bluegap.ch>
	<4136ffa0906030508i2971790dk54a8203ee03ed196@mail.gmail.com>
	<4A266A56.2020703@anarazel.de>
	<4136ffa0906030701x200bf0e4o4c77fa3239062ca5@mail.gmail.com>
	<e51f66da0906030720u33d72d05y14ea5ce002cbaf1e@mail.gmail.com>
	<20090604114610.808217tbogts0noi@mail.bluegap.ch>
	<4A283A8D.8030600@cheapcomplexdevices.com>
	<20090605090514.11712ntlvhi2deay@mail.bluegap.ch>
	<2871.1244209112@sss.pgh.pa.us> <4A2922E8.1090505@dunslane.net>
	<4A2A8E16.2090703@bluegap.ch> <11108.1244306521@sss.pgh.pa.us>
In-Reply-To: <11108.1244306521@sss.pgh.pa.us>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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/535
X-Sequence-Number: 139590

Hi,

Tom Lane wrote:
> There are a number of possible reasons, but here are a few that hold for me:

Thank you for this very good collection. I'm still wondering about
what's the best way to represent this in git (or others). Cherry-picking
is arguably the simplest variant. Maybe that can be combined with
merging to preserve merge capability. I'll try that...

> So there are a lot of good reasons to work backwards in patching.

Agreed and understood. However, there are good reasons for keeping merge
capability between branches intact as well. I still hope we can get both
somehow, if not, I'm certainly accepting that backward patching is more
important.

Regards

Markus Wanner