From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, w^3 <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Github commit messages to pgsql-www |
Date: | 2011-01-26 16:34:15 |
Message-ID: | 18354.1296059655@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 01/26/2011 10:56 AM, Tom Lane wrote:
>> 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.
> I'm not sure where the original design bit comes in. I was involved
> heavily in setting up pgfoundry (not sure if that's a claim to fame or
> infamy, but my excuse is that Josh shanghaied me) and this has been part
> of its behaviour from the start, IIRC.
Well, how come creation of a foo project results in automatic creation
of a foo-committers list there, if there was no expectation of ever
actually using that list? I know this is still happening because it
happened last week when I set up pg_filedump at pgfoundry. I was rather
annoyed when I found out that the commit traffic actually went to
pgsql-committers.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2011-01-26 16:41:49 | Re: Github commit messages to pgsql-www |
Previous Message | Andrew Dunstan | 2011-01-26 16:20:58 | Re: Github commit messages to pgsql-www |