Re: Commitfest app vs. pgsql-docs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commitfest app vs. pgsql-docs
Date: 2021-05-19 19:35:00
Message-ID: 3506449.1621452900@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Wed, May 19, 2021 at 7:39 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.

Ah. Personally, I'd settle for it checking -hackers, -docs and -bugs.
Perhaps there's some case for -general as well.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2021-05-19 19:39:53 Re: Commitfest app vs. pgsql-docs
Previous Message Andrew Dunstan 2021-05-19 19:25:55 Re: pg_rewind fails if there is a read only file.