From: Li Wang <liwang@ubuntukylin.com>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: coverity scan - a plea for help!
Date: Fri, 01 Nov 2013 08:38:52 +0800 [thread overview]
Message-ID: <5272F81C.80805@ubuntukylin.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1310311627020.5407@cobra.newdream.net>
Hi Sage,
If you trust, I think we can try this job.
Cheers,
Li Wang
On 11/01/2013 07:30 AM, Sage Weil wrote:
> Hi everyone,
>
> When I send this out several months ago, Danny Al-Gaaf stepped up and
> submitted an amazing number of patches cleaning up the most concerning
> issues that Coverity had picked up. His attention has been directed
> elsewhere more recently, but there are still a number of outstanding
> issues in Coverity's tracker that are reasonably quick and easy to resolve
> and will make our ability to identify newly introduced defects much
> simpler.
>
> Coverity Scan makes it really easy to participate: just create an account
> and I can grant you access to the Ceph project. If you're interested in
> contributing here (and it's an easy way to quickly start working with the
> Ceph code), let me know!
>
> Thanks-
> sage
>
>
> On Thu, 9 May 2013, Sage Weil wrote:
>
>> 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
>>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-11-01 0:38 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
2013-05-09 20:45 ` Sage Weil
2013-10-31 23:30 ` Sage Weil
2013-11-01 0:38 ` Li Wang [this message]
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=5272F81C.80805@ubuntukylin.com \
--to=liwang@ubuntukylin.com \
--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.