| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: commitfest.postgresql.org is no longer fit for purpose |
| Date: | 2024-05-20 08:16:24 |
| Message-ID: | 4C2E52B4-D0F7-4DC9-879A-9C4BD07448B9@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 20 May 2024, at 07:49, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> We're actually
> halfway to Gitlab et al already, with a web account and interaction
> required to start the process of submitting a patch for consideration.
Another Web<->Mailinglist extreme is Git themselves who have a Github bridge
for integration with their usual patch-on-mailinglist workflow.
https://github.com/gitgitgadget/gitgitgadget
> What I'm less clear on is who else has come up with the "bitrot" test
> idea, either at the mailing list or web extremist ends of the scale.
Most web based platforms like Github register the patch against the tree at the
time of submitting, and won't refresh unless the user does so. Github does
detect bitrot and show a "this cannot be merged" error message, but it doesn't
alter any state on the PR etc.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2024-05-20 08:18:41 | Re: Pgoutput not capturing the generated columns |
| Previous Message | Richard Guo | 2024-05-20 08:12:49 | Re: Eager aggregation, take 3 |