All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Schuberth <sschuberth@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, l.s.r@web.de
Subject: Re: [PATCH v1] travis-ci: add static analysis build job to run coccicheck
Date: Sun, 16 Apr 2017 15:31:36 +0200	[thread overview]
Message-ID: <55524921-3295-90e6-6473-ae1289eeeb75@gmail.com> (raw)
In-Reply-To: <20170411072637.57369-1-larsxschneider@gmail.com>

On 2017-04-11 09:26, Lars Schneider wrote:

> Add a dedicated build job for static analysis. As a starter we only run
> coccicheck but in the future we could run Clang Static Analyzer or
> similar tools, too.

Just FYI, some time ago someone (I don't recall who) signed up Git with 
Coverity's free scan service for OSS projects:

https://scan.coverity.com/projects/git?tab=overview

Maybe it makes sense to at least link to this page, too?

-- 
Sebastian Schuberth


  reply	other threads:[~2017-04-16 13:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11  7:26 [PATCH v1] travis-ci: add static analysis build job to run coccicheck Lars Schneider
2017-04-16 13:31 ` Sebastian Schuberth [this message]
2017-04-18 19:20   ` Stefan Beller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55524921-3295-90e6-6473-ae1289eeeb75@gmail.com \
    --to=sschuberth@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=l.s.r@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.