Re: ideas for auto-processing patches

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: markwkm(at)gmail(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ideas for auto-processing patches
Date: 2007-01-18 14:22:32
Message-ID: 45AF82A8.8040102@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

markwkm(at)gmail(dot)com wrote:
>
>
>> One thing: the patch server will have to run over HTTPS - that way we
>> can know that it is who it says it is.
>
> Right, I'm not sure if the computer I'm proofing it on is the best
> place for it so I didn't bother with the HTTPS, but should be trivial
> to have it.
>

Yes, this was more by way of a "don't forget this" note. The
implementation can be happily oblivious of it, other than setting https
in the proxy for the SOAP::Lite dispatcher. From a buildfarm point of
view, we would add such SOAP params into the config file.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-01-18 14:37:12 Re: What is the motivation of include directive and
Previous Message Tatsuo Ishii 2007-01-18 13:49:53 Re: pgsql: Fix failure due to accessing an