Re: 2019-03 CF Summary / Review - Tranche #2

From: David Steele <david(at)pgmasters(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: 2019-03 CF Summary / Review - Tranche #2
Date: 2019-02-19 05:25:44
Message-ID: 9a17ad38-a441-0137-6d4c-20f641bb26c5@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/19/19 1:23 AM, Tom Lane wrote:
> Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
>> On 2/18/19 12:43 PM, Tom Lane wrote:
>>> Andres Freund <andres(at)anarazel(dot)de> writes:
>>>> It's CF app nannyism. One can't move a patch to the next CF that's
>>>> waiting-on-author. I've complained about that a number of times, but...
>
>>> So change it to another state, push it, change it again.
>
>> I'm with Andres. I found this annoying six months ago.
>
> Oh, I agree the restriction is stupid. I'm just pointing out that
> it can be gotten around.

OK, yeah, that worked. For some reason I was having trouble moving
things out of the 2019-01 CF last month but this time it worked just
fine. I think more than one was marked as open then, not sure.

--
-David
david(at)pgmasters(dot)net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Shawn Debnath 2019-02-19 05:54:28 Re: Change of email address
Previous Message Tom Lane 2019-02-19 05:09:16 Re: Prevent extension creation in temporary schemas