Re: Automating Coverity, was Re: [PATCH 00/26] Address a couple of issues identified by Coverity

Hi Stefan, On Wed, 10 May 2017, Stefan Beller wrote: > On Wed, May 10, 2017 at 12:48 PM, Johannes Schindelin > wrote: > > > > On Fri, 5 May 2017, Johannes Schindelin wrote: > > > >> On Fri, 28 Apr 2017, Johannes Schindelin wrote: > >> > >> > On Fri, 28 Apr 2017,

Re: Automating Coverity, was Re: [PATCH 00/26] Address a couple of issues identified by Coverity

On Wed, May 10, 2017 at 12:48 PM, Johannes Schindelin wrote: > Hi Stefan, > > On Fri, 5 May 2017, Johannes Schindelin wrote: > >> On Fri, 28 Apr 2017, Johannes Schindelin wrote: >> >> > On Fri, 28 Apr 2017, Stefan Beller wrote: >> > >> > > On Thu, Apr 27, 2017 at 3:50

Re: Automating Coverity, was Re: [PATCH 00/26] Address a couple of issues identified by Coverity

Hi Stefan, On Fri, 5 May 2017, Johannes Schindelin wrote: > On Fri, 28 Apr 2017, Johannes Schindelin wrote: > > > On Fri, 28 Apr 2017, Stefan Beller wrote: > > > > > On Thu, Apr 27, 2017 at 3:50 PM, Johannes Schindelin > > > wrote: > > > > > > > I still have to

Re: Automating Coverity, was Re: [PATCH 00/26] Address a couple of issues identified by Coverity

Hi Stefan, On Fri, 28 Apr 2017, Johannes Schindelin wrote: > On Fri, 28 Apr 2017, Stefan Beller wrote: > > > On Thu, Apr 27, 2017 at 3:50 PM, Johannes Schindelin > > wrote: > > > > > I still have to find the time to figure out one more detail: how to > > >

Re: Automating Coverity, was Re: [PATCH 00/26] Address a couple of issues identified by Coverity

Hi Lars, On Mon, 1 May 2017, Lars Schneider wrote: > Looks like Coverity has TravisCI integration and I assume you wouldn't > need to worry about downloading the tool in that setup: > https://scan.coverity.com/travis_ci Except for that tiny little fact that Travis CI does not support Windows

Re: Automating Coverity, was Re: [PATCH 00/26] Address a couple of issues identified by Coverity

> On 28 Apr 2017, at 22:29, Johannes Schindelin > wrote: > > Hi Stefan, > > On Fri, 28 Apr 2017, Stefan Beller wrote: > >> On Thu, Apr 27, 2017 at 3:50 PM, Johannes Schindelin >> wrote: >> >>> I still have to find the time to figure

Automating Coverity, was Re: [PATCH 00/26] Address a couple of issues identified by Coverity

Hi Stefan, On Fri, 28 Apr 2017, Stefan Beller wrote: > On Thu, Apr 27, 2017 at 3:50 PM, Johannes Schindelin > wrote: > > > I still have to find the time to figure out one more detail: how to > > download and extract the Coverity tool (the .zip archive has a > >

Re: [PATCH 00/26] Address a couple of issues identified by Coverity

Hi Johannes, thanks for the reply. On Thu, Apr 27, 2017 at 3:50 PM, Johannes Schindelin wrote: > I still have to find the time to figure out one more detail: how to > download and extract the Coverity tool (the .zip archive has a variable > name for the top-level

Re: [PATCH 00/26] Address a couple of issues identified by Coverity

Hi Hannes, On Thu, 27 Apr 2017, Johannes Sixt wrote: > Am 26.04.2017 um 22:19 schrieb Johannes Schindelin: > > I recently registered the git-for-windows fork with Coverity to ensure > > that even the Windows-specific patches get some static analysis love. > > > > While at it, I squashed a couple

Re: [PATCH 00/26] Address a couple of issues identified by Coverity

Hi Stefan, On Wed, 26 Apr 2017, Stefan Beller wrote: > On Wed, Apr 26, 2017 at 1:19 PM, Johannes Schindelin > wrote: > > I recently registered the git-for-windows fork with Coverity to ensure > > that even the Windows-specific patches get some static analysis love. >

Re: [PATCH 00/26] Address a couple of issues identified by Coverity

Am 26.04.2017 um 22:19 schrieb Johannes Schindelin: I recently registered the git-for-windows fork with Coverity to ensure that even the Windows-specific patches get some static analysis love. While at it, I squashed a couple of obvious issues in the part that is not Windows-specific. Thanks

Re: [PATCH 00/26] Address a couple of issues identified by Coverity

On Wed, Apr 26, 2017 at 1:19 PM, Johannes Schindelin wrote: > I recently registered the git-for-windows fork with Coverity to ensure > that even the Windows-specific patches get some static analysis love. YAY! How do you trigger the coverity scan? (via travis or

[PATCH 00/26] Address a couple of issues identified by Coverity

I recently registered the git-for-windows fork with Coverity to ensure that even the Windows-specific patches get some static analysis love. While at it, I squashed a couple of obvious issues in the part that is not Windows-specific. Note: while this patch series squashes some of those issues,