From: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: coverity scan - a plea for help!
Date: Thu, 09 May 2013 22:31:30 +0200 [thread overview]
Message-ID: <518C07A2.1030806@bisect.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1305090922300.4023@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
Hi Sage,
I would like to take a look at the issues.
Danny
Am 09.05.2013 18:26, schrieb Sage Weil:
> We were added to coverity's awesome scan program a while back, which gives
> free access to their static analysis tool to open source projects.
>
> Currently it identifies 421 issues. We've already taken care of the ones
> that are highest impact, but the usefulness of periodic scans is limited
> until we can eliminate the noise from the remaining issues and easily see
> when new problems come up.
>
> If anybody is interested in helping out in the cleanup effort, let me know
> and I'll share the login info. This would provide significant value to
> our overall quality efforts and is a pretty easy way to make a meaningful
> contribution to the project without a huge investment in understanding the
> code and architecture!
>
> sage
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2013-05-09 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 16:26 coverity scan - a plea for help! Sage Weil
2013-05-09 17:15 ` Travis Rhoden
2013-05-09 20:31 ` Danny Al-Gaaf [this message]
2013-05-09 20:45 ` Sage Weil
2013-10-31 23:30 ` Sage Weil
2013-11-01 0:38 ` Li Wang
2013-11-01 1:58 ` Xing Lin
2013-11-01 15:49 ` Sage Weil
2013-11-01 16:14 ` Sage Weil
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=518C07A2.1030806@bisect.de \
--to=danny.al-gaaf@bisect.de \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.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 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.