From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, John McNamara <john.mcnamara@intel.com>
Subject: Re: [PATCH v2] devtools: add script to get maintainers from patch
Date: Wed, 08 Nov 2017 00:35:46 +0100 [thread overview]
Message-ID: <3010398.kuAIiaT0df@xps> (raw)
In-Reply-To: <20170804140125.76823-1-ferruh.yigit@intel.com>
04/08/2017 16:01, Ferruh Yigit:
> 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 path 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>
Sorry for having missed this very convenient patch for months.
Applied, thanks
Have you tried to send a patch to Linux
in order to avoid the workaround below?
> +FILES="COPYING CREDITS Kbuild"
> +FOLDERS="Documentation arch include fs init ipc kernel scripts"
> +
> +# Kernel script checks for some files and folders to run
> +workaround () {
> + for f in $FILES; do
> + if [ ! -f $f ]; then touch $f; fi
> + done
> +
> + for d in $FOLDERS; do
> + if [ ! -d $d ]; then mkdir $d; fi
> + done
> +}
next prev parent reply other threads:[~2017-11-07 23:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 16:34 [PATCH] devtools: add script to get maintainers from patch Ferruh Yigit
2017-07-06 10:37 ` Jerin Jacob
2017-08-03 10:54 ` Thomas Monjalon
2017-08-04 14:01 ` [PATCH v2] " Ferruh Yigit
2017-11-07 23:35 ` Thomas Monjalon [this message]
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=3010398.kuAIiaT0df@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.