mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Amit Kucheria <amit.kucheria@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	Andy Gross <andy.gross@linaro.org>,
	marc.w.gonzalez@free.fr,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	"David S. Miller" <davem@davemloft.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	nicolas.ferre@microchip.com, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v1 1/1] MAINTAINERS: update list of qcom drivers
Date: Mon, 17 Dec 2018 16:28:02 -0800	[thread overview]
Message-ID: <f0b650bf6bcf81c56f9624cdc3dbf65e158c677b.camel@perches.com> (raw)
In-Reply-To: <CAP245DWOSoZ4qXQ-CgUPdRQhHyg6X_7i9h0ctwafGXYS2yZLZQ@mail.gmail.com>

On Tue, 2018-12-18 at 00:20 +0530, Amit Kucheria wrote:
> On Mon, Dec 17, 2018 at 10:51 PM Joe Perches <joe@perches.com> wrote:
> > git history is used by default for the N: entries and that can
> > cause whitespace style commit authors to be cc'd on various changes
> > to matched files.
> 
> Is that by design?

yes.

> Or can we fix get_maintainer.pl to be less
> sensitive to whitespace authorship?

Use get_maintainer.pl's --nogit-fallback option



  reply	other threads:[~2018-12-18  0:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1545063166.git.amit.kucheria@linaro.org>
2018-12-17 16:19 ` Amit Kucheria
2018-12-17 16:29   ` Marc Gonzalez
2018-12-17 17:21   ` Joe Perches
2018-12-17 18:50     ` Amit Kucheria
2018-12-18  0:28       ` Joe Perches [this message]
2018-12-18  7:42   ` Kalle Valo
2018-12-18  9:21     ` Marc Gonzalez
2018-12-18 10:09       ` Kalle Valo
2018-12-18 10:01     ` Amit Kucheria

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=f0b650bf6bcf81c56f9624cdc3dbf65e158c677b.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=amit.kucheria@linaro.org \
    --cc=andy.gross@linaro.org \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.w.gonzalez@free.fr \
    --cc=mchehab+samsung@kernel.org \
    --cc=nicolas.ferre@microchip.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

all inboxes | Powered by JetHome®