Re: 2021-09 Commitfest - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: 2021-09 Commitfest
Date
Msg-id CABUevEzkNH_FDufp2cUQNebji1XWcWjg8m7AD6hMYXFVG8sYuA@mail.gmail.com
Whole thread Raw
In response to Re: 2021-09 Commitfest  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: 2021-09 Commitfest
List pgsql-hackers


On Mon, Oct 4, 2021 at 3:05 PM Daniel Gustafsson <daniel@yesql.se> wrote:
> On 4 Oct 2021, at 14:56, Magnus Hagander <magnus@hagander.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... 

--

pgsql-hackers by date:

Previous
From: Shruthi Gowda
Date:
Subject: Re: preserving db/ts/relfilenode OIDs across pg_upgrade (was Re: storing an explicit nonce)
Next
From: Jacob Champion
Date:
Subject: Re: [PATCH] Print error when libpq-refs-stamp fails