| From: | Jacob Champion <jchampion(at)timescale(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, James Coleman <jtc331(at)gmail(dot)com>, Greg Nancarrow <gregn4422(at)gmail(dot)com>, Hou Zhijie <houzj(dot)fnst(at)fujitsu(dot)com>, Mats Kindahl <mats(at)timescale(dot)com>, "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>, Denis Hirn <denis(dot)hirn(at)uni-tuebingen(dot)de>, Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>, Konstantin Knizhnik <knizhnik(at)garret(dot)ru>, Daniil Zakhlystov <usernamedt(at)yandex-team(dot)ru> |
| Subject: | Re: [Commitfest 2022-07] Patch Triage: Waiting on Author |
| Date: | 2022-07-26 23:30:01 |
| Message-ID: | faa7fac8-2b35-f05e-21e9-38d81f8e0928@timescale.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/26/22 16:20, Justin Pryzby wrote:
> I suggest that, if you send an email when marking as RWF, to mention that the
> existing patch record can be re-opened and moved to next CF.
>
> I'm aware that people may think that this isn't always a good idea, but it's
> nice to mention that it's possible. It's somewhat comparable to starting a new
> thread (preferably including a link to the earlier one).
Thanks, will do!
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Coleman | 2022-07-26 23:47:31 | Re: [Commitfest 2022-07] Patch Triage: Waiting on Author |
| Previous Message | Tom Lane | 2022-07-26 23:22:52 | Re: Is RecoveryConflictInterrupt() entirely safe in a signal handler? |