Re: ideas for auto-processing patches

From: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: markwkm(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: ideas for auto-processing patches
Date: 2007-01-05 03:57:55
Message-ID: Pine.LNX.4.58.0701051456250.4447@linuxworld.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 4 Jan 2007, Andrew Dunstan wrote:

> 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.

Right... my comment was more for Mark.

> > It would be nice if there could be a class of trusted users whose patches
> > would not have to be vetted.
> >
> >
>
> Beyond committers?

Hmmm... good question. I think so. I imagine the group would be small
though.

Thanks,

Gavin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-01-05 04:02:15 Re: Tabs or Spaces
Previous Message Tom Lane 2007-01-05 03:48:40 Re: InitPostgres and flatfiles question