Re: Patch Submission Guidelines

From: Mark Wong <markw(at)osdl(dot)org>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Patch Submission Guidelines
Date: 2006-03-22 15:52:32
Message-ID: 200603221550.k2MFocDZ016319@smtp.osdl.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Tue, 14 Feb 2006 21:54:12 +0000
Simon Riggs <simon(at)2ndquadrant(dot)com> 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.

Sorry I've gotten into this late. The PLM developed at OSDL might be
useful here. We're still grabbing daily snapshots from CVS and patches
could be submitted against those to see if they apply cleanly. Sparse
is also run but no compiling is done, although that could be easily
arranged.

Here a link:
http://plm.osdl.org/plm-cgi/plm

Mark

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message William ZHANG 2006-03-22 15:53:54 Re: Modular Type Libraries: was A real currency type
Previous Message Thomas Hallgren 2006-03-22 14:31:59 Recursive calls to functions that return sets

Browse pgsql-patches by date

  From Date Subject
Next Message Luke Lonergan 2006-03-22 16:19:40 Re: Automatically setting work_mem
Previous Message Tom Lane 2006-03-22 15:35:26 Re: WAL logging of SELECT ... INTO command