Re: INS/UPD/DEL Returning P.tch - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: INS/UPD/DEL Returning P.tch
Date
Msg-id 36e682920603021423k3f34b7b3ibe83b99d613bcfb2@mail.gmail.com
Whole thread Raw
In response to Re: INS/UPD/DEL Returning P.tch  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: INS/UPD/DEL Returning P.tch  (Neil Conway <neilc@samurai.com>)
List pgsql-hackers
If this is the consensus, then I'm fine with posting to -patches... I just want to make sure people are aware of it so it can get tested.  Thanks.

On 3/2/06, Alvaro Herrera <alvherre@commandprompt.com> wrote:
Jonah H. Harris wrote:
> All,
>
> This is only the current patch updated to apply cleanly on cvs... it's not
> ready for -patches yet as I still haven't spent much time looking through it
> and testing it.  This is just for anyone to play with and find issues.

Somebody else already did this in the last few days -- post a patch to
-hackers instead of -patches, claiming that since it's not ready, it's
not suitable for the latter.  I think this is a mistake; a patch is a
patch, whether it's ready for application or not, so it should be posted
to pgsql-patches.  You can of course indicate that the patch is a
work-in-progress and that it shouldn't be applied yet.

Anyway thanks for the patch,

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.



--
Jonah H. Harris, Database Internals Architect
EnterpriseDB Corporation
732.331.1324

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: INS/UPD/DEL Returning P.tch
Next
From: Neil Conway
Date:
Subject: Re: INS/UPD/DEL Returning P.tch