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

From Daniel Gustafsson
Subject Re: 2021-09 Commitfest
Date
Msg-id 2EDDB9BB-CCC8-4BDA-9B27-236CAE6E6787@yesql.se
Whole thread Raw
In response to Re: 2021-09 Commitfest  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
> On 4 Oct 2021, at 18:51, Magnus Hagander <magnus@hagander.net> wrote:
>
> On Mon, Oct 4, 2021 at 3:05 PM Daniel Gustafsson <daniel@yesql.se <mailto:daniel@yesql.se>> wrote:
> > On 4 Oct 2021, at 14:56, Magnus Hagander <magnus@hagander.net <mailto: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
suchcases, sadly). I ask because I'm failing to reproduce this one...  

It was on the very same entry and I only tested that one, so it sounds likely
that it was a message that was late to the party.

--
Daniel Gustafsson        https://vmware.com/




pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: [PATCH] Print error when libpq-refs-stamp fails
Next
From: Jaime Casanova
Date:
Subject: RfC entries in CF 2021-09