From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [COVERITY ACCESS] Request for access to Coverity Date: Mon, 11 May 2015 10:59:46 +0100 Message-ID: <1431338386.8263.6.camel@citrix.com> References: <20150511091306.GA30997@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YrkV4-0007Ik-Ci for xen-devel@lists.xenproject.org; Mon, 11 May 2015 09:59:50 +0000 In-Reply-To: <20150511091306.GA30997@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org On Mon, 2015-05-11 at 10:13 +0100, Wei Liu 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 late 2012; I'm now release manager for Xen > 4.6 and a maintainer for Xen tool stack. > > I would like access so that I can keep an eye on possible defects > (especially defects with security implications) and fix them in a > timely manner. +1 > > Wei Liu > > [0] http://xenproject.org/help/contribution-guidelines.html > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel