public inbox for [email protected]  

help / color / mirror / Atom feed

From: Joshua D. Drake <[email protected]>
To: Tom Lane <[email protected]>
Cc: Theo Schlossnagle <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: [email protected]
Cc: Josh Berkus <[email protected]>
Cc: Bruce Momjian <[email protected]>
Subject: Re: Getting a move on for 8.2 beta
Date: Sat, 02 Sep 2006 09:11:06 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Tom Lane wrote:
> Theo Schlossnagle <[email protected]> writes:
>> Additionally, what problem is accepting incremental patches supposed  
>> to solve?
> 
> Keeping the individual patches reviewable is one useful goal.
> 
> We may be talking at cross-purposes here.  The sort of thing I think
> Alvaro is imagining is something like what I did a year or two back when
> I wanted to make the executor treat plan trees as read-only --- if
> memory serves, I did that in three or four commits spread over a week or
> two. 

To second this, Alvaro is constantly beating our (cmd) other developers 
to do this, so I would guess that you are correct :).

I find also that this method allows someone like me, who can read C and 
understand good parts of it to get the gist of what is going on without 
trying to grok the whole thing. Large patches make it very difficult.

Sincerely,

Joshua D. Drake


-- 

    === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
    Providing the most comprehensive  PostgreSQL solutions since 1997
              http://www.commandprompt.com/

view thread (101+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Getting a move on for 8.2 beta
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox