From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel@lists.xensource.com
Subject: Re: [COVERITY ACCESS] Request for access to Coverity
Date: Thu, 25 Feb 2016 10:07:00 +0000 [thread overview]
Message-ID: <1456394820.6225.184.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1602121452170.27008@kaball.uk.xensource.com>
On Fri, 2016-02-12 at 14:53 +0000, Stefano Stabellini wrote:
> I agree to the conditions in the XenProject Coverity contribution
> guidelines [0].
>
> I'm a developer working for Citrix Systems UK, Ltd. I've been active
> in the Xen community since 2008; I currently maintain Xen on ARM, Xen
> support for the ARM and ARM64 architectures in Linux and Xen support in
> QEMU.
>
> I would like access to keep an eye on outstanding defects and help fix
> them whenever I can.
Two +1's and no objections after well more than the week required for
consultations so I've asked Coverity to send you an invitation.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-25 10:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 14:53 [COVERITY ACCESS] Request for access to Coverity Stefano Stabellini
2016-02-12 14:56 ` Andrew Cooper
2016-02-12 15:51 ` Konrad Rzeszutek Wilk
2016-02-25 10:07 ` Ian Campbell [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-11 9:13 Wei Liu
2015-05-11 9:22 ` Andrew Cooper
2015-05-11 9:59 ` Ian Campbell
2015-05-11 10:40 ` Konrad Rzeszutek Wilk
2014-11-27 15:11 Konrad Rzeszutek Wilk
2014-12-02 15:10 ` George Dunlap
2014-12-02 15:12 ` Ian Campbell
2014-12-02 17:06 ` Konrad Rzeszutek Wilk
2014-12-09 12:34 ` Ian Campbell
2014-11-27 11:39 George Dunlap
2014-11-27 11:47 ` Ian Campbell
2014-11-27 11:53 ` Andrew Cooper
2014-11-27 11:59 ` Tim Deegan
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=1456394820.6225.184.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--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 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).