Re: Further Coverity info

2013-04-10 Thread James Hunt
On 09/04/13 22:28, Scott Ritchie wrote: > On 4/9/13 7:34 AM, Allan LeSage wrote: >> * As part of our Jenkins CI program, we're Coverity-scanning merge >> proposals, and disapproving them upon finding a new defect: >> https://code.launchpad.net/~mrazik/unico/coverity/+merge/156877 . > > As an upstr

Re: Further Coverity info

2013-04-09 Thread Scott Ritchie
On 4/9/13 7:34 AM, Allan LeSage wrote: * As part of our Jenkins CI program, we're Coverity-scanning merge proposals, and disapproving them upon finding a new defect: https://code.launchpad.net/~mrazik/unico/coverity/+merge/156877 . As an upstream (wine) that uses Coverity, I'm curious how we ca

Further Coverity info

2013-04-09 Thread Allan LeSage
Hi all, I've just joined this mailing list so please forgive my failure to reply inline to an existing Coverity thread--I was just relaying some info to James and thought I'd share here as well. In Product Strategy (at Canonical) we do Coverity scanning on Unity and have developed some speci