From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "刘劲松(凯耳)" <jinsong.liu@alibaba-inc.com>
Cc: JBeulich@suse.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 2/2] Change Xen POWER MANAGEMENT maintainer email
Date: Wed, 9 Apr 2014 11:36:21 -0400 [thread overview]
Message-ID: <20140409153621.GB6604@phenom.dumpdata.com> (raw)
In-Reply-To: <000801cf5408$66ccc0c0$34664240$@alibaba-inc.com>
On Wed, Apr 09, 2014 at 11:28:47PM +0800, 刘劲松(凯耳) wrote:
> >From 6d2b2e8583d11131e7bd8aede8a3b221a5cd36f0 Mon Sep 17 00:00:00 2001
>
You might want to just do an attachment. Outlook is horrible
when it comes to sending patches.
> From: Liu Jinsong <jinsong.liu@alibaba-inc.com>
>
> Date: Thu, 10 Apr 2014 06:18:29 +0800
>
> Subject: [PATCH 2/2] Change Xen POWER MANAGEMENT maintainer email
>
>
>
> Change Xen POWER MANAGEMENT maintainer email since Jinsong switch to Alibaba
> Corp.
>
>
>
> Signed-off-by: Liu Jinsong <jinsong.liu@alibaba-inc.com>
>
> ---
>
> MAINTAINERS | 2 +-
>
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
>
> diff --git a/MAINTAINERS b/MAINTAINERS
>
> index 80fd81a..1c09ce4 100644
>
> --- a/MAINTAINERS
>
> +++ b/MAINTAINERS
>
> @@ -233,7 +233,7 @@ F: tools/ocaml/
>
>
>
> POWER MANAGEMENT
>
> M: Jan Beulich <jbeulich@suse.com>
>
> -M: Liu Jinsong <jinsong.liu@intel.com>
>
> +M: Liu Jinsong <jinsong.liu@alibaba-inc.com>
>
> S: Supported
>
> F: xen/arch/x86/acpi/
>
> X: xen/arch/x86/acpi/boot.c
>
> --
>
> 1.8.2.1
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-04-09 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 15:28 [PATCH 2/2] Change Xen POWER MANAGEMENT maintainer email 刘劲松(凯耳)
2014-04-09 15:36 ` Konrad Rzeszutek Wilk [this message]
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=20140409153621.GB6604@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=jinsong.liu@alibaba-inc.com \
--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 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.