From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, w^3 <pgsql-www(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: Github commit messages to pgsql-www |
Date: | 2011-01-26 16:03:21 |
Message-ID: | 1296057696-sup-5184@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Excerpts from Tom Lane's message of mié ene 26 12:56:57 -0300 2011:
> Personally I think there is way too much third-party crap showing up on
> pgsql-committers already. I am very close to changing my filters to
> bit-bucket *everything* out of pgfoundry, and you can bet that if stuff
> from github starts being allowed through, it will go straight to
> /dev/null here.
+1
> What I'd like to see is a reversion to the original design wherein
> commit traffic for pgfoundry projects goes to lists for those individual
> projects. As for github, people who want to watch that can watch it,
> but please don't clutter pgsql-committers with it.
+1
I would even clean up the old Majordomo archives so that the pgfoundry
stuff is elsewhere ... except that it would change the URLs for the
remaining messages.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2011-01-26 16:20:58 | Re: Github commit messages to pgsql-www |
Previous Message | Tom Lane | 2011-01-26 15:56:57 | Re: Github commit messages to pgsql-www |