From: Joe Perches <joe@perches.com>
To: "Duda, Sebastian" <sebastian.duda@fau.de>
Cc: linux-kernel@vger.kernel.org, lukas.bulwahn@gmail.com,
ralf.ramsauer@oth-regensburg.de,
wolfgang.mauerer@oth-regensburg.de
Subject: Re: get_maintainers.pl subsystem output
Date: Tue, 23 Jul 2019 04:54:22 -0700 [thread overview]
Message-ID: <45d65cf7546fcb5f2195cc831fa60dea20098802.camel@perches.com> (raw)
In-Reply-To: <2835dfa18922905ffabafb11fca7e1d2@fau.de>
On Tue, 2019-07-23 at 09:29 +0200, Duda, Sebastian wrote:
> Hi Joe,
>
> when analyzing the patch
> `<20150128012747.824898918@linuxfoundation.org>` [1] with
https://lore.kernel.org/lkml/220150128012747.824898918@linuxfoundation.org
> `get_maintainers.pl --subsystem --status --separator , /tmp/patch`,
> there is the following output:
[]
> > Run the script with multiple invocations. once for each file
> > modified by the patch.
For example: perhaps use something like:
$ grep -h '^\+\+\+ b/' <patch> | \
sed 's@^\+\+\+ b/@@' | sort | uniq | \
while read file ; do \
./scripts/get_maintainer.pl --nogit --nogit-fallback --subsystem --status --separator , $file ; \
done
or use parallel like:
$ grep -h '^\+\+\+ b/' <patch> | \
sed 's@^\+\+\+ b/@@' | sort | uniq | \
parallel -k ./scripts/get_maintainer.pl --nogit --nogit-fallback --subsystem --status --separator ,
runtime on my system for this is
Using while read loop:
real 0m2.509s
user 0m2.236s
sys 0m0.296s
Using parallel:
real 0m1.340s
user 0m4.159s
sys 0m0.429s
prev parent reply other threads:[~2019-07-23 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 7:35 Duda, Sebastian
2019-07-19 8:50 ` Joe Perches
2019-07-19 9:54 ` Duda, Sebastian
2019-07-19 14:31 ` Joe Perches
2019-07-23 7:29 ` Duda, Sebastian
2019-07-23 8:42 ` Lukas Bulwahn
2019-07-23 11:18 ` Joe Perches
2019-07-23 13:25 ` Lukas Bulwahn
2019-07-23 13:33 ` Joe Perches
2019-07-23 11:54 ` Joe Perches [this message]
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=45d65cf7546fcb5f2195cc831fa60dea20098802.camel@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=ralf.ramsauer@oth-regensburg.de \
--cc=sebastian.duda@fau.de \
--cc=wolfgang.mauerer@oth-regensburg.de \
/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
all inboxes | Powered by JetHome®