agora inbox for [email protected]  

help / color / mirror / Atom feed

From: Robert Lor <[email protected]>
To: Tom Lane <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: Joshua D. Drake <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Commitfest process
Date: Fri, 07 Mar 2008 16:22:24 -0600
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]>

Tom Lane wrote:
> This is reasonable for the sort of medium-to-large patch that the author
> has put a lot of time into.  But we also get a lot of small one-off
> patches where it's not so reasonable.  Now of course many of those get
> applied right away, but not all.  One of the services that Bruce's patch
> queue has always performed is making sure stuff like that doesn't fall
> through the cracks.  I don't think a purely author-driven patch queue
> will work to ensure that.
>
> We could combine the ideas: encourage authors to use the wiki, but have
> someone (probably Bruce ;-)) in charge of adding stuff to the wiki if
> the author doesn't.
>   
Stefan Kaltenbrunner said a script can be written to insert an entry 
into the wiki automatically when a new patch comes in. That would be 
ideal and would avoid manual intervention. The author can still update 
the wiki as needed.

http://archives.postgresql.org/pgsql-hackers/2008-02/msg00433.php


Regards,
-Robert

view thread (17+ 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]
  Subject: Re: Commitfest process
  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