| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "rejected" vs "returned with feedback" in new CF app |
| Date: | 2015-04-08 02:57:27 |
| Message-ID: | CA+TgmobFExETd8OzjkLLPut6dgCF+LR4SktD3bZGXipVKF2-Bg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 7, 2015 at 3:35 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On 4/7/15 3:33 PM, Tom Lane wrote:
>> I tried to mark the "UPDATE SET (*)" patch as "returned with feedback",
>> but the CF app informed me that if I did that the patch would
>> automatically be moved to the next commitfest. That seems completely
>> stupid. There is no need to reconsider it unless a new version of the
>> patch is forthcoming (which there may or may not ever be, but that's
>> beside the point for now). When and if the author does submit a new
>> patch, that would be the time to include it in the next commitfest, no?
>
> I noticed that as well and have avoided closing some patches because of it.
Several people, including me, have complained about this before. I
hope that Magnus will fix it soon.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2015-04-08 03:02:54 | Re: libpq's multi-threaded SSL callback handling is busted |
| Previous Message | Peter Eisentraut | 2015-04-08 02:55:58 | Re: [PATCH] Add transforms feature |