Re: ideas for auto-processing patches - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: ideas for auto-processing patches
Date
Msg-id 4078.24.211.165.134.1167968081.squirrel@www.dunslane.net
Whole thread Raw
In response to Re: ideas for auto-processing patches  (Gavin Sherry <swm@linuxworld.com.au>)
Responses Re: ideas for auto-processing patches  (Gavin Sherry <swm@linuxworld.com.au>)
Re: ideas for auto-processing patches  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
List pgsql-hackers
Gavin Sherry wrote:
>
> With PLM, you could test patches against various code branches. I'd
> guessed Mark would want to provide this capability. Pulling branches from
> anonvcvs regularly might be burdensome bandwidth-wise. So, like you say, a
> local mirror would be beneficial for patch testing.


I think you're missing the point. Buildfarm members already typically have
or can get very cheaply a copy of each branch they build (HEAD and/or
REL*_*_STABLE).  As long as the patch feed is kept to just patches which
they can apply there should be no great bandwidth issues.

>
>> The patches would need to be vetted first, or no sane buildfarm owner
>> will
>> want to use them.
>
> It would be nice if there could be a class of trusted users whose patches
> would not have to be vetted.
>
>

Beyond committers?

cheers

andrew



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: 8.3 pending patch queue
Next
From: Tom Lane
Date:
Subject: Re: InitPostgres and flatfiles question