Re: Commitfest app vs. pgsql-docs - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Commitfest app vs. pgsql-docs
Date
Msg-id CABUevEy-9QVEkx5Gr5mtBX8Uqmp-MGqv3TvCYZX3gjp8mToTTw@mail.gmail.com
Whole thread Raw
In response to Re: Commitfest app vs. pgsql-docs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Commitfest app vs. pgsql-docs
Re: Commitfest app vs. pgsql-docs
List pgsql-hackers
On Wed, May 19, 2021 at 7:39 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Stephen Frost <sfrost@snowman.net> writes:
> > * Laurenz Albe (laurenz.albe@cybertec.at) wrote:
> >> Since we have a "documentation" section in the commitfest, it would
> >> be useful to allow links to the -docs archives.
>
> > ... or get rid of the pgsql-docs mailing list, as has been suggested
> > before.
>
> IIRC, the CF app also rejects threads on pgsql-bugs, which is even
> more pointlessly annoying.  Couldn't we just remove that restriction
> altogether, and allow anything posted to some pgsql list?

It's not technically rejecting anything, it's just explicitly looking
in -hackers and doesn't even know the others exist :)

Changing that to look globally can certainly be done. It takes a bit
of work I think, as there are no API endpoints today that will do
that, but those could be added.

But just to be clear -- "some pgsql list" would include things like
pgsql-general, the pgadmin lists, the non-english regional lists, etc.
That may be fine, I just want to be sure everybody realizes that's
what it means. Basically everything on
https://www.postgresql.org/list/

-- 
 Magnus Hagander
 Me: https://www.hagander.net/
 Work: https://www.redpill-linpro.com/



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: SSL Tests for sslinfo extension
Next
From: Nitin Jadhav
Date:
Subject: Re: Removed extra memory allocations from create_list_bounds