From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com> |
Cc: | Joe Conway <mail(at)joeconway(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Audit of logout |
Date: | 2014-07-02 21:20:05 |
Message-ID: | 20140702212005.GC6390@eldon.alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Abhijit Menon-Sen wrote:
> At 2014-07-02 16:47:16 -0400, alvherre(at)2ndquadrant(dot)com wrote:
> >
> > If we expect that the author is going to update the patch, the right
> > state to use is "Waiting on author".
>
> Quite so. That's how I understand it, and what I've been doing. But what
> if we really *don't* expect the author to update the patch, but they do
> it anyway? That's the only case I was referring to.
>
> If the right thing to do is to open an entry in the next CF (as you said
> earlier in your mail), that's all right with me.
As Tom says I think we should be open to the possibility that we made a
mistake and that it should return to "needs review", when reasonable.
For example if the author takes long to update and we're in the final
steps of closing the commitfest, I don't think we need to feel forced to
re-examine the patch in the same commitfest.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2014-07-02 21:23:31 | Re: Audit of logout |
Previous Message | Abhijit Menon-Sen | 2014-07-02 21:15:42 | Re: Audit of logout |