From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Strange assertion using VACOPT_FREEZE in vacuum.c |
Date: | 2015-03-17 18:17:07 |
Message-ID: | CABUevEwzA68MQokRNKNRe8CyHwq9jSmTrKE9fdxDrPJyTmDrKQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 17, 2015 at 6:31 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> * Alvaro Herrera (alvherre(at)2ndquadrant(dot)com) wrote:
> > I went to change this patch status in the commitfest app, and the app
> > told me I cannot change the status in the current commitfest. Please
> > somebody with commitfest mace superpowers set it as ready for committer.
>
> I'm afraid the issue is a business decision which is incorrect as it's
> complaining that it's in a "Closed" state and you're trying to change it
> to an "Open" state. While it's neat to think a patch could never be
> reopened, it's clearly not accurate.
>
> Adding Magnus to this, as I'm pretty sure he has some code to go hack
> (or perhaps just remove.. :).
>
I could've sworn I'd fixed that, but pretty obviously I hadn't. Sorry about
that.
Fixed now - a patch can now go from closed back to open in the last
commitfest where it was closed.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Brightwell | 2015-03-17 18:17:20 | Re: One question about security label command |
Previous Message | Alvaro Herrera | 2015-03-17 18:13:47 | Re: Install shared libs in lib/ and bin/ with MSVC (Was: install libpq.dll in bin directory on Windows / Cygwin) |