From: Andrew Dunstan <andrew@dunslane.net>
To: Aidan Van Dyk <aidan@highrise.ca>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: Fri, 05 Jun 2009 14:41:01 -0400
Message-ID: <4A2966BD.10509@dunslane.net> (raw)
In-Reply-To: <20090605182822.GC10839@yugib.highrise.ca>
References: <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>
<20090605182822.GC10839@yugib.highrise.ca>
Aidan Van Dyk wrote:
> * Andrew Dunstan <andrew@dunslane.net> [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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: andrew@dunslane.net, aidan@highrise.ca, tgl@sss.pgh.pa.us, heikki.linnakangas@enterprisedb.com, magnus@hagander.net
Subject: Re: PostgreSQL Developer meeting minutes up
In-Reply-To: <4A2966BD.10509@dunslane.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox