Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 278F163442E for ; Sat, 6 Jun 2009 20:29:34 -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 68985-08 for ; Sat, 6 Jun 2009 20:29:32 -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 2CD326343ED for ; Sat, 6 Jun 2009 20:29:33 -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; Sun, 07 Jun 2009 01:29:29 +0200 id 000000000255C028.000000004A2AFBD9.00005207 Message-ID: <4A2AFBD8.2040000@bluegap.ch> Date: Sun, 07 Jun 2009 01:29:28 +0200 From: Markus Wanner User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Greg Stark CC: Tom Lane , Robert Haas , Ron Mayer , Marko Kreen , Andres Freund , Aidan Van Dyk , Heikki Linnakangas , Magnus Hagander , Andrew Dunstan , PostgreSQL-development Subject: Re: PostgreSQL Developer meeting minutes up References: <20090526144812.GC15213@yugib.highrise.ca> <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> <603c8f070906050829m1eaaa969tff7ca85d04018c5a@mail.gmail.com> <4888.1244216273@sss.pgh.pa.us> <4136ffa0906061115p1ff2ac36hebad6774a4e31bed@mail.gmail.com> In-Reply-To: <4136ffa0906061115p1ff2ac36hebad6774a4e31bed@mail.gmail.com> 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/539 X-Sequence-Number: 139594 Hi, Greg Stark wrote: > For what it's worth that's certainly not true. Any user maintaining a > patched version of the source tree for production use will want to > merge in any patches for older releases. For example anyone using the > CONNECT BY patch with 8.3 will surely want to take any 8.3 patch > releases. ..or port that forward to 8.4, once it's released. To me it doesn't seem that unreasonable to develop something on top of a stable branch and to want to migrate that to a newer stable branch or HEAD later on. Git could certainly help to reduce bit-rotting here, in my experience. Regards Markus Wanner