[EMAIL PROTECTED] (Marc Munro) writes:
> On Mon, 2007-30-04 at 08:56 -0300, Heikki Linnakangaspgsql wrote:
>> Date: Mon, 30 Apr 2007 09:18:36 +0100
>> From: Heikki Linnakangas <[EMAIL PROTECTED]>
>> To: Tom Lane <[EMAIL PROTECTED]>
>> Cc: Dave Page <[EMAIL PROTECTED]>, Simon Riggs
>> <[EMAIL PROTECTED]>,
>> Bruce Momjian <[EMAIL PROTECTED]>,
>> PostgreSQL-development <firstname.lastname@example.org>
>> Subject: Re: Feature freeze progress report
>> Message-ID: <[EMAIL PROTECTED]>
>> If we had a 1-2 lines status blurp attached to each patch in the
>> like "waiting for review", "author is fixing issue XX", etc., that
>> help. Bruce would need to do that if we keep the current patch queue
>> system unmodified otherwise, or we'd need to switch to something else.
> Would it be possible to also automatically determine some sort of
> bit-rot status? What I had in mind was an automated process that would
> apply each patch to HEAD on a daily basis and report whether the patch
> still applies cleanly and still allows all regression tests to pass on
> at least one platform. If and when the result of these tests changes
> from pass to fail, the patch submitter would be automatically
> The patch status could then also show the last time at which the patch
> applied cleanly, and the last time that regression tests ran
Hmm. That would be an interesting extension to the build farm.
If only the timing were right for us to get a GSoC person or something
such to add such functionality...
let name="cbbrowne" and tld="acm.org" in String.concat "@" [name;tld];;
"Lisp is an eternal thought in the mind of God."
--Crassus, mutatis mutandi
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend