| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com> |
| Subject: | Re: Windows CFBot is broken because ecpg dec_test.c error |
| Date: | 2025-02-05 21:39:25 |
| Message-ID: | CAGECzQRTo3xguwQyOAeLpYb22P9RjBwdFdEigO+oNjNhTj_zeg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 5 Feb 2025 at 21:05, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> For reference, you meant 53 right?
Yes, I meant 53
> If the
> CFBot always need one in "Future" state we should document that to make sure we
> don't miss that going forward (and perhaps automate it to make sure we dont
> make manual work for ourselves).
Afaict it doesn't need at least one in the "Future" state, instead it
needs one after the current[1] commitfest. I don't think it should
rely on that though. So I created an issue to fix that[2].
It does seem silly that we require people to manually create new
commitfests though, so I created an issue to track that[3]
[1]: https://commitfest.postgresql.org/current/
[2]: https://github.com/macdice/cfbot/issues/22
[3]: https://github.com/postgres/pgcommitfest/issues/25
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2025-02-05 21:46:09 | Re: Optimization for lower(), upper(), casefold() functions. |
| Previous Message | Peter Eisentraut | 2025-02-05 21:25:35 | Remove useless casts to (char *) |