Re: get_maintainers.pl subsystem output

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