From: Joe Perches <joe@perches.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] get_maintainer: Remove uses of P: for maintainer name
Date: Wed, 05 Feb 2020 22:47:32 -0800 [thread overview]
Message-ID: <973a8964e7d8b8a98ec34c4efa8e2726cd88013a.camel@perches.com> (raw)
In-Reply-To: <CAPcyv4g65_Jxv3GUHsTtH6KmR=AYbx4s+TAC+tLE8YeLNiH8pw@mail.gmail.com>
On Wed, 2020-02-05 at 20:14 -0800, Dan Williams wrote:
> On Wed, Feb 5, 2020 at 7:23 PM Joe Perches <joe@perches.com> wrote:
> > commit 1ca84ed6425f ("MAINTAINERS: Reclaim the P: tag for
> > Maintainer Entry Profile") changed the use of the "P:" tag
> > from "Person" to "Profile (ie: special subsystem coding styles
> > and characteristics)"
> >
> > Change how get_maintainer.pl parses the "P:" tag to match.
>
> Looks ok to me:
>
> Acked-by: Dan Williams <dan.j.william@intel.com>
>
> ...although I was not able to trigger any unexpected results running
> against drivers/nvdimm/.
Because there aren't any entries like
P: First Last
M: maintainer@domain.tld
where the name was a P: entry and the
email address was on the next line.
That was the form before 2009, but there
were still a few entries until you changed
them recently.
A long time ago:
commit 8b58be884a9fd650abb7f7adf3f885fb9cecd79d
Author: Joe Perches <joe@perches.com>
Date: Wed Jul 29 15:04:30 2009 -0700
MAINTAINERS: coalesce name and email address lines
Switch the MAINTAINERS email address format from
P: Linus Torvalds
M: torvalds@linux-foundation.org
to
M: Linus Torvalds <torvalds@linux-foundation.org>
prev parent reply other threads:[~2020-02-06 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 3:22 Joe Perches
2020-02-06 4:14 ` Dan Williams
2020-02-06 6:47 ` Joe Perches [this message]
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=973a8964e7d8b8a98ec34c4efa8e2726cd88013a.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.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 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®