From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id 7D72C5AFC for ; Fri, 23 Jan 2015 15:18:26 +0100 (CET) Received: from hmsreliant.think-freely.org ([2001:470:8:a08:7aac:c0ff:fec2:933b] helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1YEf3z-0003RV-Is; Fri, 23 Jan 2015 09:18:24 -0500 Date: Fri, 23 Jan 2015 09:18:18 -0500 From: Neil Horman To: Thomas Monjalon Message-ID: <20150123141818.GA12120@hmsreliant.think-freely.org> References: <1422017653-31442-1-git-send-email-thomas.monjalon@6wind.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1422017653-31442-1-git-send-email-thomas.monjalon@6wind.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Score: -2.9 (--) X-Spam-Status: No Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] maintainers: start a Linux-style file X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2015 14:18:26 -0000 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 > --- > 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 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?