Re: Patch Submission Guidelines - Mailing list pgsql-hackers

From Martijn van Oosterhout
Subject Re: Patch Submission Guidelines
Date
Msg-id 20060214221725.GG2435@svana.org
Whole thread Raw
In response to Re: Patch Submission Guidelines  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Tue, Feb 14, 2006 at 09:54:12PM +0000, Simon Riggs wrote:
> On Tue, 2006-02-14 at 16:17 -0500, Andrew Dunstan wrote:
>
> > If I had enough time there are all sorts of things like this I'd love to
> > set up. A fetchable url that says "try these experimental CVS branches"
> > or something like that would be great.
>
> How much time would you need? I think having every patch built before
> anyone even looks at the code would sort out most of the issues I
> mentioned.

Indeed. I was thinking of downloading the pgbuildfarm code, setting up
an autoresponder for -patches and have it autocompile patches on
submission. I've never looked at the code so I have no idea how hard it
is to set it up, but it doesn't seem that difficult.

> I'm thinking in that direction for performance testing.

Is there any standard stuff (besides maybe pgbench) that could be run?

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Patch Submission Guidelines
Next
From: Tom Lane
Date:
Subject: Re: Patch Submission Guidelines