| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 2021-09 Commitfest |
| Date: | 2021-10-04 16:51:56 |
| Message-ID: | CABUevEzkNH_FDufp2cUQNebji1XWcWjg8m7AD6hMYXFVG8sYuA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 4, 2021 at 3:05 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> > On 4 Oct 2021, at 14:56, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
> > Ugh. i missed one of the two checks. That's what I get for not testing
> properly when the change "was so simple"...
> >
> > Please try again.
>
> It works now, I was able to move a patch (3128) over to the 2021-11 CF. It
> does bring up the below warning(?) in a blue bar when the move was
> performed
> which at first made me think it hadn't worked.
>
> "The status of this patch cannot be changed in this commitfest. You
> must
> modify it in the one where it's open!"
>
Did you try it with more than one patch? It could be a held back message
that got delivered late (yes, there are some such cases, sadly). I ask
because I'm failing to reproduce this one...
--
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 | Jacob Champion | 2021-10-04 17:02:11 | Re: [PATCH] Print error when libpq-refs-stamp fails |
| Previous Message | Shruthi Gowda | 2021-10-04 16:44:21 | Re: preserving db/ts/relfilenode OIDs across pg_upgrade (was Re: storing an explicit nonce) |