Received: from maia.hub.org (maia-1.hub.org [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 9EBEE63247B for ; Fri, 14 May 2010 11:06:13 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 05940-01 for ; Fri, 14 May 2010 14:05:52 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zql.com (3a.1f.de.static.xlhost.com [206.222.31.58]) by mail.postgresql.org (Postfix) with ESMTP id AD87B63217E for ; Fri, 14 May 2010 11:06:01 -0300 (ADT) Received: from localhost ([127.0.0.1]) by zql.com with smtp (Exim 4.68) (envelope-from ) id 1OCvWZ-00036g-OD; Fri, 14 May 2010 10:06:00 -0400 From: "Greg Sabino Mullane" To: pgsql-hackers@postgresql.org Subject: Re: List traffic X-PGP-Key: 2529 DF6A B8F7 9407 E944 45B4 BC9B 9067 1496 4AC8 X-Request-PGP: http://www.biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 In-Reply-To: Date: Fri, 14 May 2010 14:05:59 -0000 X-Mailer: JoyMail 2.4.0 Message-ID: <90cc3663b615a43b8011a6337bafd9f3@biglumber.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201005/753 X-Sequence-Number: 162416 -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > ... is there a reason why, other the fact that we don't do now, that we > can't just put in a restriction against cross posting altogether? Because that would be shooting ourselves in the foot. Cross-posting is often desirable. If we had a clearer distinction of list topics, I might support such a move, but we don't, so I can't. > ... and, for those that have been here awhile, who "should know better", > why isn't there any self-management of this sort of stuff in the first > place? What would you have us do? - -- Greg Sabino Mullane greg@turnstep.com End Point Corporation http://www.endpoint.com/ PGP Key: 0x14964AC8 201005141005 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkvtWKwACgkQvJuQZxSWSsimYACgrPesGj6yxfo49c6T1PPLrKir oPoAn0b81VrrrqAozXnPXV/5vzlAuxr1 =11EB -----END PGP SIGNATURE-----