Re: Patch Submission Guidelines

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Patch Submission Guidelines
Date: 2006-02-14 21:17:57
Message-ID: 43F24905.9010401@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Martijn van Oosterhout wrote:

>Finally, several of the patches committed the last few days have been
>fixing minor bugs or platform specific issues with various patches. One
>thing that would be really nice is a real patch queue and have the
>buildfarm machines occasionally apply one of the patches and try to run
>with it. For people that don't have access to all sorts of
>architechtures, it would be a great way of getting feedback on the
>portability of the patch prior to actual submission to -HEAD.
>
>
>

This would probably be fairly trivial to arrange. There is nothing
magical about the branches we build against on buildfarm - it just
happens to be HEAD and the REL_foo_STABLE branches. They are just names
in a config file.

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.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2006-02-14 21:54:12 Re: Patch Submission Guidelines
Previous Message Martijn van Oosterhout 2006-02-14 21:00:50 Re: Patch Submission Guidelines

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Klosterman 2006-02-14 21:35:28 Re: BUG #2246: Bad malloc interactions: ecpg, openssl
Previous Message Andrew Klosterman 2006-02-14 21:15:17 Re: BUG #2246: Bad malloc interactions: ecpg, openssl