From: Frank Rowand <frowand.list@gmail.com>
To: Joe Perches <joe@perches.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] get_maintainer: Prepare for separate MAINTAINERS files
Date: Sun, 6 Aug 2017 19:16:49 -0700 [thread overview]
Message-ID: <5987CD91.6000503@gmail.com> (raw)
In-Reply-To: <51db101dddcde3115a6e834293cb1d79a2381a68.1501907539.git.joe@perches.com>
On 08/04/17 21:45, Joe Perches wrote:
> Allow for MAINTAINERS to become a directory and if it is,
> read all the files in the directory for maintained sections.
>
> Optionally look for all files named MAINTAINERS in directories
> excluding the .git directory by using --find-maintainer-files.
>
> This optional feature adds ~.3 seconds of CPU on an Intel
> i5-6200 with an SSD.
>
> Miscellanea:
>
> o Create a read_maintainer_file subroutine from the existing code
> o Test only the existence of MAINTAINERS, not whether it's a file
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
< snip >
Hi Joe,
In the three versions of this patch, I have not seen any description
of what is wrong with the current single MAINTAINERS file, or why the
proposed change is an improvement. Could you please add that
information?
-Frank
next prev parent reply other threads:[~2017-08-07 2:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 4:45 [PATCH V3] get_maintainer: Prepare for separate MAINTAINERS files Joe Perches
2017-08-07 2:16 ` Frank Rowand [this message]
2017-08-07 3:32 ` Joe Perches
2017-08-07 19:33 ` Frank Rowand
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=5987CD91.6000503@gmail.com \
--to=frowand.list@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.