Re: Commitfest Update

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Commitfest Update
Date: 2022-03-31 12:53:07
Message-ID: 202203311253.2xdtmafnmbqp@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022-Mar-31, Matthias van de Meent wrote:

> I know that this has happened earlier; where someone re-opened their
> old RwF-patches in closed commitfests; after which those patches got
> lost in the traffic because they are not open in the current (or
> upcoming) commitfests.

Hmm, it's quite possible that an explicit action "move to next CF" is
required. I don't really know what actions are allowed, though.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-03-31 13:05:52 Re: Logical insert/update/delete WAL records for custom table AMs
Previous Message Robert Haas 2022-03-31 12:39:19 Re: CLUSTER on partitioned index