From: Jason Wang <jasowang@redhat.com>
To: peter.maydell@linaro.org, qemu-devel@nongnu.org
Cc: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
Jason Wang <jasowang@redhat.com>
Subject: [Qemu-devel] [PULL 07/18] MAINTAINERS: Update mail address for COLO Proxy
Date: Fri, 8 Sep 2017 10:05:13 +0800 [thread overview]
Message-ID: <1504836324-4871-8-git-send-email-jasowang@redhat.com> (raw)
In-Reply-To: <1504836324-4871-1-git-send-email-jasowang@redhat.com>
From: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
My Fujitsu mail account will be disabled soon, update the mail info
to my private mail.
Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index caf7e8a..36eeb42 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1577,7 +1577,7 @@ F: include/migration/failover.h
F: docs/COLO-FT.txt
COLO Proxy
-M: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
+M: Zhang Chen <zhangckid@gmail.com>
M: Li Zhijian <lizhijian@cn.fujitsu.com>
S: Supported
F: docs/colo-proxy.txt
--
2.7.4
next prev parent reply other threads:[~2017-09-08 2:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 2:05 [Qemu-devel] [PULL 00/18] Net patches Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 01/18] net/filter-rewriter.c: Fix rewirter checksum bug when use virtio-net Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 02/18] net/rocker: Remove the dead error handling Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 03/18] net/rocker: Plug memory leak in pci_rocker_init() Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 04/18] net/rocker: Convert to realize() Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 05/18] net/rocker: Fix the unusual macro name Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 06/18] net: rtl8139: do not use old_mmio accesses Jason Wang
2017-09-08 2:05 ` Jason Wang [this message]
2017-09-08 2:05 ` [Qemu-devel] [PULL 08/18] net/socket: Don't treat odd socket type as SOCK_STREAM Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 09/18] net/socket: Convert several helper functions to Error Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 10/18] net/net: Convert parse_host_port() " Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 11/18] net/socket: Improve -net socket error reporting Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 12/18] e1000: Rename the SEC symbol to SEQEC Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 13/18] net/colo-compare.c: Optimize unpredictable tcp options comparison Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 14/18] net/colo-compare.c: Adjust net queue pop order for performance Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 15/18] net/colo-compare.c: Fix comments and scheme Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 16/18] qemu-iothread: IOThread supports the GMainContext event loop Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 17/18] colo-compare: Use IOThread to Check old packet regularly and Process pactkets of the primary Jason Wang
2017-09-08 2:05 ` [Qemu-devel] [PULL 18/18] colo-compare: Update the COLO document to add the IOThread configuration Jason Wang
2017-09-08 13:00 ` [Qemu-devel] [PULL 00/18] Net patches Peter Maydell
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=1504836324-4871-8-git-send-email-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=zhangchen.fnst@cn.fujitsu.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).