From: Keir Fraser <keir.xen@gmail.com>
To: Tim Deegan <tim@xen.org>,
xen-devel@lists.xensource.com, JBeulich@suse.com,
ian.jackson@citrix.com
Cc: Ian.Campbell@citrix.com
Subject: Re: Proposed new committer for ARMv7+VE
Date: Thu, 26 Jan 2012 17:16:41 +0000 [thread overview]
Message-ID: <CB473AF9.29AC3%keir.xen@gmail.com> (raw)
In-Reply-To: <20120126162621.GE80228@ocelot.phlegethon.org>
On 26/01/2012 16:26, "Tim Deegan" <tim@xen.org> wrote:
> Hi,
>
> We seem to have agreement that we can start checking in the Xen
> ARMv7-with-Virtualization-Extensions patches that Stefano has been
> posting.
>
> It's been suggested that Ian Campbell be made a committer for
> the ARMv7+VE stuff (arch/arm &c). Following the procedure at
> http://www.xen.org/projects/governance.html, I hereby nominate him.
>
> Keir, Ian, Jan, please respond with your integer of choice.
+1
> Cheers,
>
> Tim
next prev parent reply other threads:[~2012-01-26 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 16:26 Proposed new committer for ARMv7+VE Tim Deegan
2012-01-26 16:42 ` Jan Beulich
2012-01-26 17:12 ` Ian Jackson
2012-01-26 17:16 ` Keir Fraser [this message]
2012-01-30 16:18 ` Ian Campbell
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=CB473AF9.29AC3%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.jackson@citrix.com \
--cc=tim@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 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).