Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 8E2306336C6 for ; Sat, 6 Jun 2009 12:41:13 -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 70826-07-2 for ; Sat, 6 Jun 2009 12:41:12 -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 26BD46353DF for ; Sat, 6 Jun 2009 12:41:11 -0300 (ADT) Received: from [192.168.2.103] (p5497615B.dip.t-dialin.net [::ffff:84.151.97.91]) (AUTH: CRAM-MD5 markus@bluegap.ch) by shaykin.bluegap.ch with esmtp; Sat, 06 Jun 2009 17:41:10 +0200 id 000000000255C021.000000004A2A8E16.00007D05 Message-ID: <4A2A8E16.2090703@bluegap.ch> Date: Sat, 06 Jun 2009 17:41:10 +0200 From: Markus Wanner User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Andrew Dunstan CC: Tom Lane , Ron Mayer , Marko Kreen , Greg Stark , Andres Freund , Aidan Van Dyk , Heikki Linnakangas , Magnus Hagander , PostgreSQL-development Subject: Re: PostgreSQL Developer meeting minutes up References: <20090526144812.GC15213@yugib.highrise.ca> <20090602162333.369974jcc3jpn3dx@mail.bluegap.ch> <20090602180702.15986cp384yo3l7q@mail.bluegap.ch> <20090603131004.12934iyrr4f7rlsc@mail.bluegap.ch> <4136ffa0906030508i2971790dk54a8203ee03ed196@mail.gmail.com> <4A266A56.2020703@anarazel.de> <4136ffa0906030701x200bf0e4o4c77fa3239062ca5@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> In-Reply-To: <4A2922E8.1090505@dunslane.net> 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/514 X-Sequence-Number: 139569 Hi, Andrew Dunstan wrote: > Yeah, a requirement to work from the back branch forward is quite > unacceptable IMNSHO. It's also quite unreasonable. The monotone page about daggy fixes does quite a good job in explaining why it is helpful. I think it's how to make best use of these tools. And it's obviously not the same as what worked well in practice with CVS. Out of interest, and not necessarily related to Postgres: why do you think it's unreasonable? Fixing the problem where it was introduced sounds like the most reasonable place to fix it, IMO. Regards Markus Wanner