On Mon, 2015-02-16 at 11:07 +0200, Jaak Ristioja wrote:
> On 16.02.2015 10:55, Peter von Kaehne wrote:
> > Has it changed much since this blog has been written?
> >
> > http://blog.josefsson.org/2007/04/02/boycott-scancoveritycom/
>
> Well, judge for yourself:
> https://scan.coverity.com/polic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/02/15 11:28, Matěj Cepl wrote:
> Usually the amount of false positives on the first run is quite
> drastic, but the pain can subside with some amount of healing.
My impression is that for the first year or so,the ideal course of
action, is t
On Mon, Feb 16, 2015 at 3:07 AM, Jaak Ristioja wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 16.02.2015 10:55, Peter von Kaehne wrote:
>> On Fri, 2015-02-13 at 10:54 +0200, Jaak Ristioja wrote:
>>> Hello!
>>>
>>> Has the Sword project considered running their code throught the
>>
On 2015-02-16, 08:55 GMT, Peter von Kaehne wrote:
> On Fri, 2015-02-13 at 10:54 +0200, Jaak Ristioja wrote:
>> Hello!
>>
>> Has the Sword project considered running their code throught the
>> Coverity Scan service (scan.coverity.com)? We just configured
>> BibleTime to run on Travis CI and the Cov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16.02.2015 10:55, Peter von Kaehne wrote:
> On Fri, 2015-02-13 at 10:54 +0200, Jaak Ristioja wrote:
>> Hello!
>>
>> Has the Sword project considered running their code throught the
>> Coverity Scan service (scan.coverity.com)? We just configured
On Fri, 2015-02-13 at 10:54 +0200, Jaak Ristioja wrote:
> Hello!
>
> Has the Sword project considered running their code throught the
> Coverity Scan service (scan.coverity.com)? We just configured
> BibleTime to run on Travis CI and the Coverity Scan and it found quite
> a lot of bugs in our code
