On Tue, Feb 26, 2008 at 02:57:12PM -0800, Joshua D. Drake wrote:
If we get volunteers set up, they will start running it daily.
Would there be a way to script the responses to flag us for things
that are important?
There was (briefly) a way for them to send emails whenever something
new
On Tue, 2008-02-26 at 11:33 -0800, Josh Berkus wrote:
We need two (or more) PostgreSQL hackers to volunteer to regularly check the
Coverity reports and either fix/forward the bugs found, or (more often) mark
them as non-bugs in the Coverity system.
I take a look at this periodically.
Neil,
I take a look at this periodically. Apparently the last run of the tool
for Postgres happened on October 30th -- do you know if there's a way to
schedule more frequent runs?
If we get volunteers set up, they will start running it daily.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 26 Feb 2008 14:45:23 -0800
Josh Berkus [EMAIL PROTECTED] wrote:
Neil,
I take a look at this periodically. Apparently the last run of the
tool for Postgres happened on October 30th -- do you know if
there's a way to schedule more
On Tue, 2008-02-26 at 14:57 -0800, Joshua D. Drake wrote:
Would there be a way to script the responses to flag us for things
that are important?
I think you need human verification / analysis, which isn't an easy
thing to script.
-Neil
---(end of
On 27/02/2008, Neil Conway [EMAIL PROTECTED] wrote:
I think you need human verification / analysis, which isn't an easy
thing to script.
Is that site publicly accessible, do they have some sample
output that one could examine in regards to Joshua's parsing
idea?
-Neil
Cheers,
Andrej
--
