From: Jan Beulich <jbeulich@suse.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-api@lists.xenproject.org" <xen-api@lists.xenproject.org>,
"minios-devel@lists.xenproject.org"
<minios-devel@lists.xenproject.org>,
"committers@xenproject.org" <committers@xenproject.org>,
"mirageos-devel@lists.xenproject.org"
<mirageos-devel@lists.xenproject.org>,
xen-devel <xen-devel@lists.xenproject.org>,
"win-pv-devel@lists.xenproject.org"
<win-pv-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [Vote] For Xen Project Code of Conduct (deadline March 31st)
Date: Tue, 4 Feb 2020 14:35:34 +0100 [thread overview]
Message-ID: <9f2c8dae-532d-5ddf-de2d-244e3c6a8531@suse.com> (raw)
In-Reply-To: <63005C11-CF8C-4794-B9E4-C3856CCF41C1@citrix.com>
On 17.01.2020 20:12, Lars Kurth wrote:
> People allowed to vote on behalf of the Hypervisor project are:
> Julien Grall, Andy Cooper, George Dunlap, Ian Jackson, Jan Beulich, Konrad R
> Wilk, Stefano Stabellini, Wei Liu and Paul Durrant (as Release Manager).
I have to admit that with certain parts of this, as per earlier discussion,
I'm on the edge, and hence I'd like to give a +0.5 vote here. Whatever you
can then make of this ...
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-02-04 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 19:12 [Xen-devel] [Vote] For Xen Project Code of Conduct (deadline March 31st) Lars Kurth
2020-01-17 19:33 ` Lars Kurth
2020-01-22 21:16 ` Stefano Stabellini
2020-01-23 9:38 ` Durrant, Paul
2020-01-27 12:16 ` George Dunlap
2020-01-27 12:26 ` Wei Liu
2020-01-27 15:13 ` Ian Jackson
2020-02-04 13:35 ` Jan Beulich [this message]
2020-02-11 12:44 ` [Xen-devel] UPDATE " George Dunlap
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=9f2c8dae-532d-5ddf-de2d-244e3c6a8531@suse.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=committers@xenproject.org \
--cc=ian.jackson@eu.citrix.com \
--cc=minios-devel@lists.xenproject.org \
--cc=mirageos-devel@lists.xenproject.org \
--cc=win-pv-devel@lists.xenproject.org \
--cc=xen-api@lists.xenproject.org \
--cc=xen-devel@lists.xenproject.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.