| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | "rejected" vs "returned with feedback" in new CF app |
| Date: | 2015-04-07 19:33:38 |
| Message-ID: | 28144.1428435218@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 ended up marking it "rejected" instead, but that seems a bit harsh.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2015-04-07 19:35:31 | Re: "rejected" vs "returned with feedback" in new CF app |
| Previous Message | Tom Lane | 2015-04-07 19:22:18 | Re: Support UPDATE table SET(*)=... |