From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Helin Zhang <helin.zhang@intel.com>, thomas@monjalon.net
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] maintainers: change maintainership
Date: Tue, 26 Jun 2018 10:04:55 +0100 [thread overview]
Message-ID: <42f14e41-863d-855c-3003-39798f141c5f@intel.com> (raw)
In-Reply-To: <1529658839-20499-1-git-send-email-helin.zhang@intel.com>
On 6/22/2018 10:13 AM, Helin Zhang wrote:
> Xiaoyun Li has agreed to take over the maintainership of example
> application tep_termination, as Jijiang Liu is no longer working
> on that.
>
> Signed-off-by: Helin Zhang <helin.zhang@intel.com>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Thanks Xiaoyun for volunteering.
prev parent reply other threads:[~2018-06-26 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1529658839-20499-1-git-send-email-helin.zhang@intel.com>
[not found] ` <8a858c3b-c638-e594-31b5-47b5f44f2fb4@intel.com>
2018-06-22 15:32 ` Thomas Monjalon
2018-06-26 9:04 ` Ferruh Yigit [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=42f14e41-863d-855c-3003-39798f141c5f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=thomas@monjalon.net \
/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).