From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jeffrey Karrels <karrelsj@gmail.com>
Cc: xen-devel@lists.xensource.com, lars.kurth@xen.org
Subject: Re: Static analysis: Code weaknesses
Date: Fri, 16 Mar 2012 11:51:32 -0400 [thread overview]
Message-ID: <20120316155132.GB31099@phenom.dumpdata.com> (raw)
In-Reply-To: <CAFw--Dcrw4vxWY44X4mOT0JUEfGbQVa6XtPYNEL_ieSNSRHzxg@mail.gmail.com>
On Fri, Mar 16, 2012 at 08:44:16AM -0700, Jeffrey Karrels wrote:
> > I will check it out. It is free, but I am not sure how much
> > functionality one gets. We will see.
> > http://scan.coverity.com/developers-faq.html
>
> To keep track of this topic, the coverity scanner project will not
> accept the GPLv2 license for acceptance to the project because of
> Xen's association with Citrix. I will continue to work on our
> licensed analyzers and post patches back into the community, it is
> just a little harder to collaborate...
>
> "As you may well have read in our Developer FAQ, license is only one of the
> criteria that determines eligibility, and the association between Xen and
> Citrix is close enough that I think Xen doesn't qualify."
Huh? That really does not compute - as there are developers who are not
Citrix employeed - and the sources/trees, etc are all on xenbits.org which
is a non-prof organization I think? CC-ing Lars here as he might know better.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-03-16 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 18:10 Static analysis: Code weaknesses Jeffrey Karrels
2012-03-13 16:47 ` Konrad Rzeszutek Wilk
2012-03-13 17:03 ` Dario Faggioli
2012-03-14 18:01 ` Jeffrey Karrels
2012-03-14 18:58 ` Konrad Rzeszutek Wilk
2012-03-14 19:14 ` Jeffrey Karrels
2012-03-16 15:44 ` Jeffrey Karrels
2012-03-16 15:51 ` Konrad Rzeszutek Wilk [this message]
2012-03-16 16:10 ` Jeffrey Karrels
2012-09-05 20:13 ` Jeffrey Karrels
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=20120316155132.GB31099@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=karrelsj@gmail.com \
--cc=lars.kurth@xen.org \
--cc=xen-devel@lists.xensource.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.