From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] devtools: add script to get maintainers from patch
Date: Thu, 6 Jul 2017 16:07:52 +0530 [thread overview]
Message-ID: <20170706103751.GA5907@jerin> (raw)
In-Reply-To: <20170428163420.25785-1-ferruh.yigit@intel.com>
-----Original Message-----
> Date: Fri, 28 Apr 2017 17:34:20 +0100
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> To: Thomas Monjalon <thomas@monjalon.net>
> CC: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
> Subject: [dpdk-dev] [PATCH] devtools: add script to get maintainers from
> patch
> X-Mailer: git-send-email 2.8.4
>
> This is a wrapper to Linux kernel get_maintainer.pl file and only
> supports parsing MAINTAINERS file (no git fallback etc..)
>
> Requires DPDK_GETMAINTAINER_PATH devel config option set, please check
> devtools/load-devel-config.
>
> DPDK_GETMAINTAINER_PATH should be full patch to the get_maintainer.pl
> script, like:
> DPDK_GETMAINTAINER_PATH=~/linux/scripts/get_maintainer.pl
>
> Can be used individually:
> ./devtools/get_maintainer.sh <my.patch>
>
> Or via git send-email, to add maintainers automatically:
> git send-email --to-cmd ./devtools/get_maintainer.sh \
> --cc dev@dpdk.org HEAD -4
>
> Currently there is an ugly workaround to be able to use Linux script out
> of the kernel tree, later better method can replace it.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Cool stuff.
Should we also update the contribution guide for this scheme? so
that it will increase the chance for maintainers to get the direct email and
enable more timely patch review.
Tested-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
next prev parent reply other threads:[~2017-07-06 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 16:34 Ferruh Yigit
2017-07-06 10:37 ` Jerin Jacob [this message]
2017-08-03 10:54 ` Thomas Monjalon
2017-08-04 14:01 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2017-11-07 23:35 ` Thomas Monjalon
2017-11-07 23:41 ` Ferruh Yigit
2017-11-07 23:45 ` 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=20170706103751.GA5907@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).