From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Laura Abbott <labbott@redhat.com>, linux-kernel@vger.kernel.org
Cc: Wolfram Sang <wsa@the-dreams.de>,
Lee Jones <lee.jones@linaro.org>, Joe Perches <joe@perches.com>
Subject: Re: [PATCH] get_maintainer: Don't fallback to git by default
Date: Tue, 27 Oct 2015 09:08:12 +0900 [thread overview]
Message-ID: <562EC06C.5010404@osg.samsung.com> (raw)
In-Reply-To: <562EB07B.9040501@redhat.com>
Hello Laura,
Thanks a lot for your feedback.
On 10/27/2015 08:00 AM, Laura Abbott wrote:
> On 10/26/2015 03:11 PM, Javier Martinez Canillas wrote:
>> The get_maintainer.pl script could be used to get a list of people that
>> has to be in the copy list when posting patches for a given file but it
>> defaults to git fallback so the list returned isn't really relevant and
>> submitters are posting patches to random developers that just happened
>> to touch that file in the past.
>>
>> Disable git fallback so get_maintainer.pl only returns the information
>> that is in MAINTAINERS by default.
>>
>> Suggested-by: Wolfram Sang <wsa@the-dreams.de>
>> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>>
>> ---
>> Hello,
>>
>> This patch was suggested by Wolfram on this thread [0] but it is
>> something I thought before because I've seen people complaining
>> on a regular basis about being cc'ed in random patches and there
>> are tools like patman [1] that rely on get_maintainers.pl to post
>> the patches.
>>
>> [0]: https://lkml.org/lkml/2015/10/26/444
>> [1]: http://git.denx.de/?p=u-boot.git;a=blob;f=tools/patman/README
>>
>> Best regards,
>> Javier
>>
>
> We might need to do a sweep of files to make sure more of them are
> listed in the maintainers file, else by default they only show LKML.
> As an example, a bunch of files in lib are only showing LKML.
> Defaulting to only sending to LKML may be swinging too far in the wrong
> direction for reducing inbox size.
>
You are correct, disabling git fallback could be a too radical solution
for now until the MAINTAINERS file is more complete.
I'll do some auditing to the files in the source tree and see if I can
come with a patch series that improves the state of MAINTAINERS before
disabling this option by default.
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2015-10-27 0:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 22:11 [PATCH] get_maintainer: Don't fallback to git by default Javier Martinez Canillas
2015-10-26 23:00 ` Laura Abbott
2015-10-27 0:08 ` Javier Martinez Canillas [this message]
2015-10-27 2:47 ` Theodore Ts'o
2015-10-27 4:57 ` joe
2015-10-27 5:03 ` Laura Abbott
2015-10-27 8:21 ` Lee Jones
2015-10-27 9:24 ` Wolfram Sang
2015-10-27 10:10 ` Lee Jones
2015-10-27 10:29 ` Wolfram Sang
2015-10-27 17:49 ` Joe Perches
2015-10-27 18:21 ` Joe Perches
2015-10-27 23:25 ` Wolfram Sang
2015-10-27 23:37 ` Joe Perches
2015-10-28 0:05 ` Wolfram Sang
2015-10-28 0:14 ` Joe Perches
2015-10-28 8:50 ` Lee Jones
2015-10-27 17:53 ` Joe Perches
2015-10-27 18:09 ` Lee Jones
2015-10-27 19:24 ` Javier Martinez Canillas
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=562EC06C.5010404@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=joe@perches.com \
--cc=labbott@redhat.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).