From: David Maxwell <dmaxwell@coverity.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Coverity checking periodicity?
Date: Wed, 18 Nov 2009 12:32:07 -0500 [thread overview]
Message-ID: <20091118173207.GB6796@mail> (raw)
In-Reply-To: <4B042C94.9070403@gmail.com>
On Wed, Nov 18, 2009 at 06:19:16PM +0100, Jiri Slaby wrote:
> On 11/18/2009 04:39 PM, David Maxwell wrote:
> > You mentioned the stats on the Scan site not being updated. That's true.
> > I haven't had time to do maintenance on the relevant scripts in quite a while,
> > so the site doesn't reflect the ongoing builds and defect count changes. :-(
>
> David, thank you for the reply. I'm just curious, are the results
> publicly available or are they visible only to few chosen people?
Hi Jiri,
Each open source project can set their own rules about how small a group
of people can have access to the results. Some projects are very
sensitive about potential security issues and keep it to a few core
folks.
Other projects are less strict. In the Linux case, I forward any
requests off to a handful of Linux people who give me a thumbs-up/down
on the request.
Generally, if I get a request from a maintainer, it has always been
approved.
--
David Maxwell
Coverity Open Source Strategist
http://scan.coverity.com/
next prev parent reply other threads:[~2009-11-18 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 15:39 Coverity checking periodicity? David Maxwell
2009-11-18 17:19 ` Jiri Slaby
2009-11-18 17:32 ` David Maxwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-17 8:34 Jiri Slaby
2009-11-18 10:34 ` Jiri Kosina
2009-11-18 10:35 ` Jiri Slaby
2009-11-18 11:45 ` Jiri Slaby
2009-11-18 11:52 ` Jiri Kosina
2009-11-18 12:02 ` Jiri Slaby
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=20091118173207.GB6796@mail \
--to=dmaxwell@coverity.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@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 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.