Re: Github commit messages to pgsql-www

Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > On Wed, Jan 26, 2011 at 15:14, Alvaro Herrera
> > <alvherre(at)commandprompt(dot)com> wrote:
> >> Could we do #3 but instead of moving the primary to git.pg.org just have
> >> a hook or cron'ed task that pushes from github (or pulls from it)?
>
> > Sure, you can do something like that, but it has the same basic
> > "scalability problem" - all the repos need to be created and
> > maintained on git.postgresql.org.
>
> > Plus it requires a push hook at github (because the mail scripts fire
> > on receive, so it needs to be a push), which I don't think they
> > support.
>
> 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.

I did that years ago. I allow only pgfoundry projects I am interested
in to flow through.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +