Re: [PATCHES] [0/4] Proposal of SE-PostgreSQL patches - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: [PATCHES] [0/4] Proposal of SE-PostgreSQL patches
Date
Msg-id 87lk4hb61c.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: [PATCHES] [0/4] Proposal of SE-PostgreSQL patches  (Greg Smith <gsmith@gregsmith.com>)
Responses Re: [PATCHES] [0/4] Proposal of SE-PostgreSQL patches  (Greg Smith <gsmith@gregsmith.com>)
Re: [PATCHES] [0/4] Proposal of SE-PostgreSQL patches  (KaiGai Kohei <kaigai@ak.jp.nec.com>)
List pgsql-hackers
"Greg Smith" <gsmith@gregsmith.com> writes:

> On Mon, 17 Mar 2008, KaiGai Kohei wrote:
>
>> I'll submit the proposal of SE-PostgreSQL patches again, because some of previous
>> messages are filtered due to attachment and I cannot provide whole of patches yet.
>
> This is actually what you should have done from the beginning.  And it only
> should have gone to the pgsql-hackers list, which is the only one I'm replying
> to.  Your patches are at this point a proposal, as you say in the subject, and
> those go to the pgsql-hackers list with the minimum of files necessary to
> support them.  pgsql-patches is generally aimed at patches that have already
> been discussed on the hackers list, ones that are basically ready to apply to
> the source code.

Some people shout any time you send patches to -hackers. For the -patches is
there mainly to catch large attachments regardless of their maturity.

But it's true that it's best to post a plan and have discussion prior to
developing big patches.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support!


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Small bug in new backend build method
Next
From: "Jochem van Dieten"
Date:
Subject: Re: Rewriting Free Space Map