Re: Github commit messages to pgsql-www

On Tue, Jan 25, 2011 at 21:24, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On Tue, Jan 25, 2011 at 7:55 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> What do we want to do with them...
>>
>> Andrew has set it up for the bulidfarm client code, and it does work,
>> except they get caught in the moderator queue - becuase they are sent
>> from noreply(at)github(dot)com(dot) The way I see it we have a couple of options
>> for making this work:
>>
>> 1) Whiltelist noreply(at)github(dot)com(dot) We have no way of controlling this
>> though, so *anybody* with a github repo can have it sent there, and
>> they all come from the same address. I don't think we can whitelist on
>> the combination of email and some part of the email,thus filtering
>> based on repo.
>>
>> 2) Just moderate the commit messages as they show up.
>>
>> 3) Ask Andrew to move the primary to git.postgresql.org and use the
>> commit message hook there, that will send the emails as the person who
>> committed the patch (like we do for pgadmin for example). This has the
>> advantage of allowing individual moderation, and the disadvantage that
>> it doesn't scale if we want to end up with lots of repositories
>> management-wise...
>>
>> Thoughts?
>>
>
> Why do we want buildfarm commit messages to come to pgsql-www?

D'uh, stupid typo on my part. Of course, I mean pgsql-committers. Sorry.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/