Moving RwF patches to a new CF

From: Jacob Champion <jchampion(at)timescale(dot)com>
To: Wenjing Zeng <wjzeng2012(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Moving RwF patches to a new CF
Date: 2022-07-15 23:16:46
Message-ID: CAAWbhmgvzgOtQG3_ut-6_ouRq4OMcZgu8RZh2xWtsdcW-H=Cwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

[changing the subject line, was "[Commitfest 2022-07] Begins Now"]

On Fri, Jul 15, 2022 at 1:37 AM Wenjing Zeng <wjzeng2012(at)gmail(dot)com> wrote:
> Please move the Global Temporary table to check next month, that is at 202208.
> I need more time to process the existing issue.

Hi Wenjing,

My current understanding is that RwF patches can't be moved (even by
the CFM). You can just reattach the existing thread to a new CF entry
when you're ready, as discussed in [1]. (Reviewers can sign themselves
back up; don't carry them over.)

It does seem annoying to have to reapply annotations, though. I would
like to see the CF app support this and I'll try to put a patch
together sometime (there's a growing list).

Thanks,
--Jacob

[1] https://www.postgresql.org/message-id/CALT9ZEGoVd6%2B5FTJ3d6DXRO4z%3DrvqK%2BdjrmgSiFo7dkKeMkyfQ%40mail.gmail.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2022-07-15 23:27:47 Re: PG15 beta1 sort performance regression due to Generation context change
Previous Message Justin Pryzby 2022-07-15 23:15:32 Re: Commitfest Update