From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: plpgsql: open for execute - add USING clause |
Date: | 2009-11-17 22:59:42 |
Message-ID: | 603c8f070911171459t45029931sfd83ddd4dd44b9ca@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 17, 2009 at 5:34 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> Pavel Stehule wrote:
>>
>> I don't wont to apply these patches tomorrow, I don't sending these
>> patches for last moment. If I have to wait one weak or two weeks, ok.
>> Declare it. I'll respect it. But actually I respecting all rules, what
>> I know.
>
> If you're sending stuff intended for the next CommitFest in the middle of an
> active one (which we'd prefer not to see at all but you have your own
> schedule limitations), it would be helpful if you were to label those
> patches as such. It's difficult for the rest of us to tell which of the
> ones you're generating are in response to patches that are active during
> this one, and which are intended for future review but you're just dropping
> them off now. Had your new stuff been labeled "This is for the next
> CommitFest, I'm just sending it to the list now", it would have made it
> easier on everyone else to figure out which of your messages we need to pay
> attention to and what should be ignored for now.
This expresses my feelings on the topic exactly, and perhaps merits
inclusion in a Wiki page someplace. Maybe we need to have a wiki page
on commitfest rules & expectations.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-11-17 23:01:52 | Re: RFC for adding typmods to functions |
Previous Message | Dimitri Fontaine | 2009-11-17 22:53:13 | Re: actualised funcs typmod patch |