From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, Dave Page <dpage(at)pgadmin(dot)org>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Policy on cross-posting to multiple lists |
Date: | 2020-09-17 19:03:46 |
Message-ID: | 237180.1600369426@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> BTW now that this is working, I think we should discuss that if person A
> cross-posts, and that post is approved, then whenever person B replies
> it should also be approved -- surely there's no need to approve the
> cross-posting (for the known subset of lists) for each reply.
If that can be automated it'd surely make things noticeably less painful.
As is, once somebody's started a multi-list thread, the only way to get
out of trouble is for someone to remember to remove other lists from a
reply ... and even then, if anyone replies to an earlier post, it's a mess
all over again. But I didn't realize we had the ability to pre-approve
whole threads for this filter?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2020-09-17 19:17:07 | Re: Policy on cross-posting to multiple lists |
Previous Message | Alvaro Herrera | 2020-09-17 18:49:23 | Re: Policy on cross-posting to multiple lists |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2020-09-17 19:17:07 | Re: Policy on cross-posting to multiple lists |
Previous Message | Alvaro Herrera | 2020-09-17 18:49:23 | Re: Policy on cross-posting to multiple lists |