From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: commitfest app moving patch error |
Date: | 2018-06-27 10:35:21 |
Message-ID: | CABUevEwcwTtTcoQ-52daoCmrK3=10dyXusJ5d4fceq4o4hhJ0A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 27, 2018 at 8:20 AM, Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> I tried to move a patch from 2018-07 to 2018-09 and got this error:
>
> "Cannot move patch to the same commitfest, and multiple future
> commitfests exist!"
>
Right. You are only supposed to "move to next cf" from one that's actually
in progress, and not be working on one that isn't :P
The rules are basically:
* If there is an open one, move it there.
* If there isn't an open one, move to the future one if there is only one.
It's really intended to work with the first one -- patches are only
supposed to be added to the one that's open...
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2018-06-27 11:11:30 | Re: Code of Conduct committee: call for volunteers |
Previous Message | Gilles Darold | 2018-06-27 10:21:16 | Re: [HACKERS] proposal: schema variables |