Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kIzPM-0006i6-8L for pgsql-www@arkaria.postgresql.org; Thu, 17 Sep 2020 19:17:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kIzPL-0007a2-1u for pgsql-www@arkaria.postgresql.org; Thu, 17 Sep 2020 19:17:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kIzPK-0007Zv-2B for pgsql-www@lists.postgresql.org; Thu, 17 Sep 2020 19:17:26 +0000 Received: from mail-lj1-x230.google.com ([2a00:1450:4864:20::230]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kIzPG-0004kL-JI for pgsql-www@lists.postgresql.org; Thu, 17 Sep 2020 19:17:24 +0000 Received: by mail-lj1-x230.google.com with SMTP id n25so3022950ljj.4 for ; Thu, 17 Sep 2020 12:17:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nIHa19HHLylCNobk0J85C58yrJvZiD836MxZNR2qsmo=; b=s8JWeXyO/jW1g4DdqrXoAaVpapxMQRDD1tgW4R+MnZhtF5j0tL7bak/smUYPvJtsL7 b667AHv6PehKH0k8dgEXDJRSnaTOYoboE8SExodAhtBR8S7C0U8XFQysanHOfgOt0V+o a27TTOnYBWZeI3J3tkEKqFat91uqu6rB2Dz9gIpyGInIyDTV5kdBlLrLttQhD0jWecMz BKU+GFYNNG925/Ggf5C+LhY8pIbtBhUcajQuwW8w18g3mfbFbFMHAdBAgZschJX1eo7H kIjEjncDfQPmMggqjt2F60zJGad95fAwl3IXNsjzm7/+awqy9DfzyZc1PRe57RBG7WZv H96w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nIHa19HHLylCNobk0J85C58yrJvZiD836MxZNR2qsmo=; b=V2gs3K0fuG5PkMJtFAyRvJuE1vxR6JxuUMF7y2HmyogIdfLTomPSb9ickb+rbLDnMW P0d2WfG2tqxyQZi+MApPEPSLg0ZvfzsnhHcdcQ4ZnpplLnpycEwWjqR0GsxrDRyouNnS KlXb4mlpKVS6AgspG9cg9rN87wHeiW2q6vuIoygnRqRjXNuALs1RkDHEwUGQCR8RH9Yh OU+2cX6j4zLq3/Cmh3J9a1J2oFz2GJtAKeEJwmiPGlp5l5TLROpAxtydpzN4JfErfq6d TEj4m15/EkPZ4Rs2bFtO2uyh0a9w96w1Ac8K/vOQT3unkxhcU/AvIJzMt5LwxopG8v5n 84Jw== X-Gm-Message-State: AOAM53020hEkqplMNN4HRy03l1iqeiMTi3hcGwSSwgFDcefrCzIM13JN V/x1fduAL2PzCsqUlxUQw9k52kY1thdSggyIZiG09w== X-Google-Smtp-Source: ABdhPJxkvHmFRnIcKp7pQdtfncGj/+oEbAEz3NkUNhR75tOLCZzO2CFw4G56xSSnST8h+j3S4Vj7qbV/I0QM44CwSQM= X-Received: by 2002:a2e:8e30:: with SMTP id r16mr11450322ljk.304.1600370239521; Thu, 17 Sep 2020 12:17:19 -0700 (PDT) MIME-Version: 1.0 References: <20200917184923.GA25665@alvherre.pgsql> <237180.1600369426@sss.pgh.pa.us> In-Reply-To: <237180.1600369426@sss.pgh.pa.us> From: Magnus Hagander Date: Thu, 17 Sep 2020 21:17:07 +0200 Message-ID: Subject: Re: Policy on cross-posting to multiple lists To: Tom Lane Cc: Alvaro Herrera , Stephen Frost , Andres Freund , Tatsuo Ishii , Dave Page , Dean Rasheed , PostgreSQL WWW Content-Type: multipart/alternative; boundary="000000000000a2dc5f05af873b96" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000a2dc5f05af873b96 Content-Type: text/plain; charset="UTF-8" On Thu, Sep 17, 2020 at 9:03 PM Tom Lane wrote: > Alvaro Herrera 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? > We don't. And I don't see an obvious way to do it either. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --000000000000a2dc5f05af873b96 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Sep 17, 2020 at 9:03 PM Tom Lane = <tgl@sss.pgh.pa.us> wrote:
Alvaro Herrera <alvherre@2ndquadrant.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 th= e
> cross-posting (for the known subset of lists) for each reply.

If that can be automated it'd surely make things noticeably less painfu= l.
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 m= ess
all over again.=C2=A0 But I didn't realize we had the ability to pre-ap= prove
whole threads for this filter?

We don&#= 39;t. And I don't see an obvious way to do it either.
=C2=A0<= /div>
--
=C2=A0Magnus Hagander
=C2=A0Me: https://www.hagander.net/
=C2=A0Work: https://www.redpill-l= inpro.com/
--000000000000a2dc5f05af873b96--