From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
Robin van der Gracht <robin@protonic.nl>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Miguel Ojeda Sandonis <miguel.ojeda.sandonis@gmail.com>,
Thierry Reding <treding@nvidia.com>,
Shawn Guo <shawnguo@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Matt Ranostay <mranostay@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"David S . Miller" <davem@davemloft.net>,
Guenter Roeck <linux@roeck-us.net>, Jiri Slaby <jslaby@suse.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: get_maintainer.pl and MAINTAINERS file
Date: Thu, 19 May 2016 13:57:43 -0300 [thread overview]
Message-ID: <20160519135743.5fc661c4@recife.lan> (raw)
In-Reply-To: <CAFLxGvwU-2aE7_0Suht--DvWby3RT=mdkpRomHz25MgicRfC3w@mail.gmail.com>
Em Thu, 19 May 2016 16:25:45 +0200
Richard Weinberger <richard.weinberger@gmail.com> escreveu:
> On Thu, May 19, 2016 at 2:57 PM, Kalle Valo <kvalo@codeaurora.org> wrote:
> > (Changed the subject from "Re: [PATCH v6 0/3] auxdisplay: Introduce ht16k33 driver")
> >
> > Robin van der Gracht <robin@protonic.nl> writes:
> >
> >>> And 4th, what is with the insane number of people on cc:? Use
> >>> get_maintainer.pl correctly please, and don't just hit everyone you
> >>> can possibly think of with a cc: for no good reason.
> >>
> >> I did use the get_maintainer script. I solely passed the patch set as
> >> command line argument.
> >
> > I think get_maintainer script should ignore MAINTAINERS file altogether.
> > After I did drivers/net/wireless reorganisation, and had to make
> > numerous changes to MAINTAINERS in the process, I have been CCed to all
> > sorts of patchsets to which I have nothing to do with (this one
> > included). I suspect get_maintainer.pl is to blame here.
>
> Are you sure it is because you are listed as maintainer for specific files?
> If you are maintain something you have to be CC'ed.
> It is rather because get_maintainer.pl tries to be smart and uses git to
> find people who have touched a file...
>
> I guess instead you want something like:
> http://permalink.gmane.org/gmane.linux.kernel.commits.head/538561
I guess what Kalle said is that the get_maintainer.pl script should
disable, by default, "--git-blame" behavior for some specific files that
everyone touches like /MAINTAINERS, Documentation/kernel-parameters.txt,
/CREDITS, etc, as random people that touch on those files aren't really
interested on being c/c to every change there.
Regards,
Mauro
next prev parent reply other threads:[~2016-05-19 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 12:23 [PATCH v6 0/3] auxdisplay: Introduce ht16k33 driver Robin van der Gracht
2016-05-18 12:23 ` [PATCH v6 1/3] of: add vendor prefix for Holtek Semiconductor Robin van der Gracht
2016-05-18 23:17 ` Rob Herring
2016-05-18 12:23 ` [PATCH v6 2/3] auxdisplay: ht16k33: Driver for LED controller Robin van der Gracht
2016-05-18 23:23 ` Rob Herring
2016-05-18 12:23 ` [PATCH v6 3/3] MAINTAINERS: auxdisplay: Added myself as maintainer for ht16k33 driver Robin van der Gracht
2016-05-18 14:32 ` Linus Walleij
2016-05-18 15:09 ` [PATCH v6 0/3] auxdisplay: Introduce " Greg Kroah-Hartman
2016-05-19 8:54 ` Robin van der Gracht
2016-05-19 12:57 ` get_maintainer.pl and MAINTAINERS file Kalle Valo
2016-05-19 14:25 ` Richard Weinberger
2016-05-19 16:57 ` Mauro Carvalho Chehab [this message]
2016-05-20 13:14 ` Kalle Valo
2016-05-19 19:53 ` Jiri Slaby
2016-05-19 22:32 ` Joe Perches
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=20160519135743.5fc661c4@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jic23@kernel.org \
--cc=jslaby@suse.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mranostay@gmail.com \
--cc=pawel.moll@arm.com \
--cc=richard.weinberger@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robin@protonic.nl \
--cc=shawnguo@kernel.org \
--cc=treding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome