| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: strange IS NULL behaviour |
| Date: | 2013-09-09 16:37:25 |
| Message-ID: | CA+TgmoZZ2NAf1iC4hYFt8o6QGvMBTxqjp_j_YkjCGr=RXRKnpA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Sep 7, 2013 at 10:59 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> Why don't you add the proposal to the commitfest?
>
> This issue is so much larger than the patch's validity that I don't see
> how that would work.
I hate to be rude here, but I think you're being ridiculous. We have
a well-established procedure for getting patches reviewed around here,
and while it is not perfect, it mostly works. If you try that
procedure and it doesn't work, then I think you have a right to
complain. But to object, on the one hand, that people aren't going to
look at the patch, and then to refuse to add it to the tracking tool
that the project uses to ensure that patches get looked at, seems
patently unfair.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-09-09 16:38:31 | Re: only linestyle is NULL as default |
| Previous Message | Robert Haas | 2013-09-09 16:21:56 | Re: [RFC] overflow checks optimized away |