| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | gabrielle <gorthx(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Mark Wong <markwkm(at)gmail(dot)com>, David Christensen <david(at)endpoint(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Explicit psqlrc |
| Date: | 2010-07-20 13:05:55 |
| Message-ID: | AANLkTi=5bTZYV5j9A+SCX=R99Kgf=yMyFz0jOR50_F58@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 20, 2010 at 8:21 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Tue, 2010-07-20 at 07:49 -0400, Robert Haas wrote:
>> A further point is that it's very difficult to
>> keep track of progress if the CF page reflects a whole bunch of
>> supposedly "Waiting on Author" patches that are really quite
>> thoroughly dead.
>
> True, but the point under discussion is what to do if no reply is
> received from an author. That is something entirely different from a
> patch hitting a brick wall.
>
> We gain nothing by moving early on author-delay situations, so I suggest
> we don't.
No, we gain something quite specific and tangible, namely, the
expectation that patch authors will stay on top of their patches if
they want them reviewed by the community. If that expectation doesn't
seem important to you, feel free to try running a CommitFest without
it. If you can make it work, I'll happily sign on.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-07-20 13:12:40 | Some git conversion issues |
| Previous Message | Pavel Stehule | 2010-07-20 12:58:24 | Re: review: psql: edit function, show function commands patch |