From: Ferruh Yigit <ferruh.yigit@intel.com>
To: ogawa.yasufumi@lab.ntt.co.jp, spp@dpdk.org
Subject: Re: [spp] [PATCH] maintainers: add MAINTAINERS
Date: Tue, 28 Nov 2017 17:26:53 -0800 [thread overview]
Message-ID: <85812886-850f-e056-e053-ed60d52727a6@intel.com> (raw)
In-Reply-To: <20171128093204.46310-1-ogawa.yasufumi@lab.ntt.co.jp>
On 11/28/2017 1:32 AM, ogawa.yasufumi@lab.ntt.co.jp wrote:
> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
>
> Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Thanks for volunteering.
> ---
> MAINTAINERS | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
> create mode 100644 MAINTAINERS
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> new file mode 100644
> index 0000000..2f7128b
> --- /dev/null
> +++ b/MAINTAINERS
> @@ -0,0 +1,28 @@
> +SPP Maintainers
> +================
> +
> +The intention of this file is to provide a set of names that we can rely on
> +for helping in patch reviews and questions.
> +These names are additional recipients for emails sent to spp@dpdk.org.
> +Please avoid private emails.
> +
> +Descriptions of section entries:
> +
> + M: Maintainer's Full Name <address@domain>
> + T: Git tree location.
> + F: Files and directories with wildcard patterns.
> + A trailing slash includes all files and subdirectory files.
> + A wildcard includes all files but not subdirectories.
> + One pattern per line. Multiple F: lines acceptable.
> + X: Files and directories exclusion, same rules as F:
> + K: Keyword regex pattern to match content.
> + One regex pattern per line. Multiple K: lines acceptable.
> +
> +
> +General Project Administration
> +------------------------------
> +
> +Main Branch
> +M: Ferruh Yigit <ferruh.yigit@intel.com>
> +M: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
> +T: git://dpdk.org/apps/spp
>
next prev parent reply other threads:[~2017-11-29 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 9:32 ogawa.yasufumi
2017-11-29 1:26 ` Ferruh Yigit [this message]
2017-11-29 1:30 ` Ferruh Yigit
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=85812886-850f-e056-e053-ed60d52727a6@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--cc=spp@dpdk.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 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).