From: Greg Sabino Mullane <greg@turnstep.com>
To: pgsql-hackers@postgresql.org
Subject: Re: List traffic
Date: Fri, 14 May 2010 14:05:59 -0000
Message-ID: <90cc3663b615a43b8011a6337bafd9f3@biglumber.com> (raw)
In-Reply-To: <alpine.BSF.2.00.1005140225310.22297@hub.org>
-----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-----
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: greg@turnstep.com, pgsql-hackers@postgresql.org
Subject: Re: List traffic
In-Reply-To: <90cc3663b615a43b8011a6337bafd9f3@biglumber.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox