MIME-Version: 1.0
References: 
 <CAEZATCVNn-nH8XOACOS2ahsz9oG_uY9GjTva0YGNodxLquyHyw@mail.gmail.com>
 <20190110171835.GP2528@tamriel.snowman.net> <3281.1547142423@sss.pgh.pa.us>
In-Reply-To: <3281.1547142423@sss.pgh.pa.us>
From: Dave Page <dpage@pgadmin.org>
Date: Thu, 10 Jan 2019 23:53:47 +0530
Message-ID: 
 <CA+OCxoxsEC78bJrkgWObfx7jDTZ_DPi7TucEZSmS4hXbZOYDTw@mail.gmail.com>
Subject: Re: Policy on cross-posting to multiple lists
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephen Frost <sfrost@snowman.net>,
 Dean Rasheed <dean.a.rasheed@gmail.com>,
	pgsql-www@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Jan 10, 2019 at 11:17 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Stephen Frost <sfrost@snowman.net> writes:
> > * Dean Rasheed (dean.a.rasheed@gmail.com) wrote:
> >> Has the policy on cross-posting to multiple lists been hardened recently?
>
> > So, the short answer is 'yes'.
> > Perhaps that hasn't been getting through to people...?
>
> If this was publicly announced anywhere, I didn't see it.
> I would have pushed back if I had.  CC'ing -hackers on a reply to
> a bug report is something I do all the time, and I do not think
> it'd be a good idea to stop doing so, nor to make the thread
> disappear from the -bugs archives.
>
> I'm quite on board with the need to reduce useless cross-posting,
> but this is not the solution.

Agreed. Similarly, posts from pgadmin-support sometimes end up
intentionally being cross posted to pgadmin-hackers.

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company