public inbox for [email protected]  

help / color / mirror / Atom feed

From: Theo Schlossnagle <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: Theo Schlossnagle <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: [email protected]
Cc: Josh Berkus <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Tom Lane <[email protected]>
Subject: Re: Getting a move on for 8.2 beta
Date: Sat, 2 Sep 2006 11:41:48 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>


On Sep 2, 2006, at 11:28 AM, Tom Lane wrote:

> Alvaro Herrera <[email protected]> writes:
>> Here's a completely novel idea: accept incremental patches.
>
> I don't think it's as novel as all that --- personally I've always
> preferred to tackle large projects incrementally.

I think that accepting incremental patches to a mainline is _bad_ and  
that accepting them in general is good (as you have to go through  
that process outside of version control sometimes anyway).  Sticking  
them in CVS however can get a bit messy.  This is where other version  
control systems that have a bit better branching and merging support  
has an advantage as people can work in the repository on their  
project in separate branches and pulling them all back together again  
(once an overall satisfaction metric has been reached) is not  
excruciatingly painful.  Where am I going with this?  From my  
experience accepting incremental patches is a _bad_ idea unless you  
have a VCS that has really makes it _easy_ to manage them.  Sounds  
like more work than worth on the postgres project as it is now.

Additionally, what problem is accepting incremental patches supposed  
to solve?

// Theo Schlossnagle
// CTO -- http://www.omniti.com/~jesus/
// OmniTI Computer Consulting, Inc. -- http://www.omniti.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]
  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