Re: antisocial things you can do in git (but not CVS)

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jonathan Corbet <corbet(at)lwn(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: antisocial things you can do in git (but not CVS)
Date: 2010-07-24 17:48:50
Message-ID: 4C4B2782.6050809@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut wrote:
> On lör, 2010-07-24 at 07:02 -0700, Ron Mayer wrote:
>
>> Instead of squashing every patch into a single commit, what if it got
>> squashed into a perhaps 3 separate commits -- one as submitted, one
>> as reviewed, and one as re-written by the committer. History stays
>> linear; and you keep the most relevant parts of the history,
>> while dropping all the development brainstorming commits.
>>
>
> But then there would be commits in the main repository that were known
> not good enough.
>
>

Yeah. Also, please bear in mind that our explicit aim here is to make
this change with a minimal disruption to existing work flows. So to all
those people who want to say "Look, you can now do all these cool
things" my answer is "Maybe we'll do them later, but not right now."

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2010-07-24 19:24:35 Re: antisocial things you can do in git (but not CVS)
Previous Message Peter Eisentraut 2010-07-24 17:28:36 Re: antisocial things you can do in git (but not CVS)