From: mailings at hupie.com (Ferry Huberts)
Subject: cgit & Coverity
Date: Thu, 15 Nov 2012 19:25:51 +0100 [thread overview]
Message-ID: <50A533AF.2000502@hupie.com> (raw)
Hi guys
How about trying to get cgit scanned by Coverity?
I recently - successfully - applied for Coverity scanning for olsrd and
must say that I like their tooling, it has found some pretty obscure
bugs and leaks. For olsrd my Jenkins server now submits every build to
Coverity, who then scan it.
What do you think?
--
Ferry Huberts
next reply other threads:[~2012-11-15 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 18:25 mailings [this message]
2012-12-02 17:29 ` Jason
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=50A533AF.2000502@hupie.com \
--to=cgit@lists.zx2c4.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).