xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Tim Deegan <tim@xen.org>
Subject: Re: [COVERITY ACCESS] Request for access to Coverity
Date: Tue, 2 Dec 2014 15:12:40 +0000	[thread overview]
Message-ID: <1417533160.24320.54.camel@citrix.com> (raw)
In-Reply-To: <CAFLBxZZKBf70oH7yUC9JDU7U3Ca5SAt6vWcNfnMy566KEPQS4w@mail.gmail.com>

On Tue, 2014-12-02 at 15:10 +0000, George Dunlap wrote:
> On Thu, Nov 27, 2014 at 3:11 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> >
> > On Nov 27, 2014 6:59 AM, Tim Deegan <tim@xen.org> wrote:
> >>
> >> At 11:39 +0000 on 27 Nov (1417084797), George Dunlap wrote:
> >> > -----BEGIN PGP SIGNED MESSAGE-----
> >> > Hash: SHA512
> >> >
> >> > I agree to the conditions in the XenProject Coverity contribution
> >> > guidelines [1].
> >> >
> >> > I'm a developer working for Citrix Systems UK, Ltd.  I've been active
> >> > in the Xen community since 2006; I was release coordinator for the 4.3
> >> > and 4.4 releases, and I am currently maintainer of the Xen scheduling
> >> > subsystem.
> >> >
> >> > I would like access primarily to be able to write and speak
> >> > intelligently about Xen and Coverity in blog postings and conference
> >> > talks.  I figure it would be easier to go through the stats and
> >> > history myself, rather than trying to get some other developer to do
> >> > it for me.  (Although of course once I have access I'll probably end
> >> > up doing some work looking at scans anyway.)
> >>
> >> +1
> >
> > +1 too.

> OK, that's +4 and no minuses after 5 days.  How long to I have to wait?  :-)

http://www.xenproject.org/help/contribution-guidelines.html says seven
days...

Ian.

  reply	other threads:[~2014-12-02 15:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27 15:11 [COVERITY ACCESS] Request for access to Coverity Konrad Rzeszutek Wilk
2014-12-02 15:10 ` George Dunlap
2014-12-02 15:12   ` Ian Campbell [this message]
2014-12-02 17:06     ` Konrad Rzeszutek Wilk
2014-12-09 12:34     ` Ian Campbell
  -- strict thread matches above, loose matches on Subject: below --
2016-02-12 14:53 Stefano Stabellini
2016-02-12 14:56 ` Andrew Cooper
2016-02-12 15:51 ` Konrad Rzeszutek Wilk
2016-02-25 10:07 ` Ian Campbell
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 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=1417533160.24320.54.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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 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).