Re: Moving RwF patches to a new CF

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Jacob Champion <jchampion(at)timescale(dot)com>, Wenjing Zeng <wjzeng2012(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Moving RwF patches to a new CF
Date: 2022-07-16 08:31:29
Message-ID: 1c8ba1cc-e0cc-b686-0e3d-9cbff719d46c@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 16.07.22 01:16, Jacob Champion wrote:
> 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.)

I think you can just change the entry back to "needs review" and then
move it forward.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-07-16 08:53:17 Re: System catalog documentation chapter
Previous Message Peter Eisentraut 2022-07-16 06:58:10 Re: Avoid unecessary MemSet call (src/backend/utils/cache/relcache.c)