From: Neil Horman <nhorman@tuxdriver.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] maintainers: start a Linux-style file
Date: Fri, 23 Jan 2015 09:18:18 -0500 [thread overview]
Message-ID: <20150123141818.GA12120@hmsreliant.think-freely.org> (raw)
In-Reply-To: <1422017653-31442-1-git-send-email-thomas.monjalon@6wind.com>
On Fri, Jan 23, 2015 at 01:54:13PM +0100, Thomas Monjalon wrote:
> This MAINTAINERS file is inspired from the Linux one.
>
> Almost all files are split into areas in order to identify maintainers of
> each DPDK area. Note that a maintainer is not a git tree manager.
> Candidates are welcome to send a patch to sign up for one or several areas.
>
> There is a script to check covering, especially when adding or moving files.
>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> ---
> MAINTAINERS | 388 +++++++++++++++++++++++++++++++++++++++++++
> scripts/check-maintainers.sh | 85 ++++++++++
> 2 files changed, 473 insertions(+)
> create mode 100644 MAINTAINERS
> create mode 100755 scripts/check-maintainers.sh
>
Acked-by: Neil Horman <nhorman@tuxdriver.com>
feel free to add me in as the AF_PACKET pmd maintainer if Linville doesn't
want the official title.
One question, the security issues list, is that active already and in use? Can
we document the membership of that list so we know who's handling security
issues?
next prev parent reply other threads:[~2015-01-23 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 12:54 Thomas Monjalon
2015-01-23 14:18 ` Neil Horman [this message]
2015-01-23 14:46 ` Thomas Monjalon
2015-01-23 15:52 ` Neil Horman
2015-01-23 18:12 ` [dpdk-dev] [PATCH] MAINTAINERS: claim responsibility for Linux AF_PACKET PMD John W. Linville
2015-01-23 18:16 ` Neil Horman
2015-01-29 21:03 ` Thomas Monjalon
2015-01-28 10:50 ` [dpdk-dev] [PATCH v2] maintainers: start a Linux-style file Thomas Monjalon
2015-01-29 20:57 ` Thomas Monjalon
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=20150123141818.GA12120@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).