From: Karel Zak <kzak@redhat.com>
To: Boris Egorov <egorov@linux.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Coverity Scan analysis report
Date: Wed, 12 Nov 2014 15:30:38 +0100 [thread overview]
Message-ID: <20141112143038.GC5530@x2.net.home> (raw)
In-Reply-To: <5462F558.5000602@linux.com>
On Wed, Nov 12, 2014 at 11:51:20AM +0600, Boris Egorov wrote:
> It is possible to analyze project using Coverity Scan. I've created a
> project on their website with my clone of util-linux on Github. You can see
> it here: https://scan.coverity.com/projects/3469?tab=overview (I can export
> report if you can't see it).
> So, it can be done for the main util-linux Github repo. Coupled with Travis
> CI it can generate regular analysis reports.
Cool, it would be nice to have the reports for our community, but
please, think twice before you fix anything, it generates many many
nonsenses.
I use Coverity for util-linux (usually for -rc releases) internally
in Red Hat. Unfortunately it's impossible to share these reports publicly.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2014-11-12 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 5:51 Coverity Scan analysis report Boris Egorov
2014-11-12 14:30 ` Karel Zak [this message]
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=20141112143038.GC5530@x2.net.home \
--to=kzak@redhat.com \
--cc=egorov@linux.com \
--cc=util-linux@vger.kernel.org \
/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).