Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 1EA2D632F34 for ; Fri, 5 Jun 2009 15:41:17 -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 11466-03 for ; Fri, 5 Jun 2009 15:41:11 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from alexis.jtlnet.com (alexis.jtlnet.com [69.36.9.81]) by mail.postgresql.org (Postfix) with ESMTP id 04FF6632A1E for ; Fri, 5 Jun 2009 15:41:13 -0300 (ADT) Received: from [192.168.10.103] (cpe-075-177-154-027.nc.res.rr.com [::ffff:75.177.154.27]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by alexis.jtlnet.com with esmtp; Fri, 05 Jun 2009 14:40:47 -0400 id 0008078D.4A2966B0.00003867 Message-ID: <4A2966BD.10509@dunslane.net> Date: Fri, 05 Jun 2009 14:41:01 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text SeaMonkey/1.0.9 MIME-Version: 1.0 To: Aidan Van Dyk CC: Tom Lane , Heikki Linnakangas , Magnus Hagander , PostgreSQL-development Subject: Re: PostgreSQL Developer meeting minutes up References: <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> <20090605182822.GC10839@yugib.highrise.ca> In-Reply-To: <20090605182822.GC10839@yugib.highrise.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.092 tagged_above=0 required=5 tests=AWL=0.092 X-Spam-Level: X-Archive-Number: 200906/484 X-Sequence-Number: 139539 Aidan Van Dyk wrote: > * Andrew Dunstan [090605 13:55]: > > >> Yeah, a requirement to work from the back branch forward is quite >> unacceptable IMNSHO. It's also quite unreasonable. The tool is there to >> help, not to force an unnatural work pattern on us. >> > > Again, just to make it clear, git isn't going to *force* anyone to > drastically change their workflow. My reaction was against someone saying in effect "don't work that way, work this way". So make your argument to that person ;-) [...] > I have a feeling that as people (specifically the comitters) get slowly > introduced and exposed to some of the more advanced things git lets you > do, and as you get comfortable with using it, people will *want* to > start altering how they do thing, simply because they start to find out > that git really allows them to do what they really want, rather than > what they have "thought they want" because they've been so brainwashed > by CVS... > > > The whole point is that we want something better *that suits our work patterns*. Almost all the backpatching that gets done is by the committers. So we have a bunch of concerns that are not relevant to that vast majority of developers. In particular, it would be nice to be able to make a bunch of changes on different branches and then commit it all in one hit. If that's possible, then well and good. If it's not, that's a pity. cheers andrew