From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] MAINTAINERS: ARM Versatile Express platform
Date: Wed, 26 Nov 2014 07:40:21 -0800 [thread overview]
Message-ID: <1417016421.19695.1.camel@perches.com> (raw)
In-Reply-To: <1417012855.3972.3.camel@arm.com>
On Wed, 2014-11-26 at 14:40 +0000, Pawel Moll wrote:
> On Wed, 2014-11-26 at 12:17 +0000, Arnd Bergmann wrote:
> > On Wednesday 26 November 2014 12:04:09 Pawel Moll wrote:
> > >
> > > Right, of course. Whole directory.
> > >
> > > > F: */*/vexpress*
> > >
> > > Cool, didn't think about multiple wildcards.
> >
> > Actually, I think you could even do this as
> >
> > N: vexpress
> >
> > which would be even shorter and match most of the other entries too.
>
> If you think it's safe, fine with me. It would reduce this section to:
>
> N: vexpress
> F: drivers/clocksource/versatile.c
Yes, that's possible too, but:
from MAINTAINERS:
scripts/get_maintainer.pl has different behavior for files that
match F: pattern and matches of N: patterns. By default,
get_maintainer will not look at git log history when an F: pattern
match occurs. When an N: match occurs, git log history is used
to also notify the people that have git commit signatures.
I think it's better to use F: entries because
there is a get_maintainer difference in behavior
between N: and F: entries.
An N: entry means get_maintainer will also cc
patch submitters for these files.
An F: entry will not.
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Pawel Moll <pawel.moll@arm.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Mike Turquette <mturquette@linaro.org>,
"arm@kernel.org" <arm@kernel.org>,
Russell King <linux@arm.linux.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Liviu Dudau <Liviu.Dudau@arm.com>,
Sudeep Holla <Sudeep.Holla@arm.com>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] MAINTAINERS: ARM Versatile Express platform
Date: Wed, 26 Nov 2014 07:40:21 -0800 [thread overview]
Message-ID: <1417016421.19695.1.camel@perches.com> (raw)
In-Reply-To: <1417012855.3972.3.camel@arm.com>
On Wed, 2014-11-26 at 14:40 +0000, Pawel Moll wrote:
> On Wed, 2014-11-26 at 12:17 +0000, Arnd Bergmann wrote:
> > On Wednesday 26 November 2014 12:04:09 Pawel Moll wrote:
> > >
> > > Right, of course. Whole directory.
> > >
> > > > F: */*/vexpress*
> > >
> > > Cool, didn't think about multiple wildcards.
> >
> > Actually, I think you could even do this as
> >
> > N: vexpress
> >
> > which would be even shorter and match most of the other entries too.
>
> If you think it's safe, fine with me. It would reduce this section to:
>
> N: vexpress
> F: drivers/clocksource/versatile.c
Yes, that's possible too, but:
from MAINTAINERS:
scripts/get_maintainer.pl has different behavior for files that
match F: pattern and matches of N: patterns. By default,
get_maintainer will not look at git log history when an F: pattern
match occurs. When an N: match occurs, git log history is used
to also notify the people that have git commit signatures.
I think it's better to use F: entries because
there is a get_maintainer difference in behavior
between N: and F: entries.
An N: entry means get_maintainer will also cc
patch submitters for these files.
An F: entry will not.
next prev parent reply other threads:[~2014-11-26 15:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 18:17 [PATCH v2 RESEND 1/2] ARM: vexpress: Remove non-DT code Pawel Moll
2014-11-25 18:17 ` Pawel Moll
2014-11-25 18:17 ` [PATCH 2/2] MAINTAINERS: ARM Versatile Express platform Pawel Moll
2014-11-25 18:17 ` Pawel Moll
2014-11-26 1:54 ` Mike Turquette
2014-11-26 1:54 ` Mike Turquette
2014-11-26 1:59 ` Joe Perches
2014-11-26 1:59 ` Joe Perches
2014-11-26 12:04 ` Pawel Moll
2014-11-26 12:04 ` Pawel Moll
2014-11-26 12:17 ` Arnd Bergmann
2014-11-26 12:17 ` Arnd Bergmann
2014-11-26 14:40 ` Pawel Moll
2014-11-26 14:40 ` Pawel Moll
2014-11-26 15:40 ` Joe Perches [this message]
2014-11-26 15:40 ` Joe Perches
2014-11-26 12:13 ` [PATCH v2] " Pawel Moll
2014-11-26 12:13 ` Pawel Moll
2014-11-28 15:14 ` Arnd Bergmann
2014-11-28 15:14 ` Arnd Bergmann
2014-11-28 17:56 ` Joe Perches
2014-11-28 17:56 ` Joe Perches
2014-12-01 13:57 ` Pawel Moll
2014-12-01 13:57 ` Pawel Moll
2014-12-01 14:16 ` [PATCH] MAINTAINERS: ARM Versatile Express platform, add missing pattern Pawel Moll
2014-12-04 16:02 ` Arnd Bergmann
2014-11-28 15:08 ` [PATCH v2 RESEND 1/2] ARM: vexpress: Remove non-DT code Arnd Bergmann
2014-11-28 15:08 ` Arnd Bergmann
2014-11-28 15:30 ` Russell King - ARM Linux
2014-11-28 15:30 ` Russell King - ARM Linux
2014-11-28 15:53 ` Pawel Moll
2014-11-28 15:53 ` Pawel Moll
2014-11-28 16:31 ` Arnd Bergmann
2014-11-28 16:31 ` Arnd Bergmann
2014-11-28 16:34 ` Pawel Moll
2014-11-28 16:34 ` Pawel Moll
2014-11-28 16:44 ` [PATCH RESEND] ARM: vexpress: Enable regulator framework when MMCI is in use Pawel Moll
2014-11-28 20:57 ` Arnd Bergmann
2014-11-28 16:48 ` [PATCH v2 RESEND 1/2] ARM: vexpress: Remove non-DT code Russell King - ARM Linux
2014-11-28 16:48 ` Russell King - ARM Linux
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=1417016421.19695.1.camel@perches.com \
--to=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.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.