From: Joe Perches <joe@perches.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Torvalds <torvalds@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Lee Jones <lee.jones@linaro.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Move entry for Cirrus Logic Madera codecs
Date: Tue, 28 Aug 2018 11:16:33 -0700 [thread overview]
Message-ID: <b160878ca73bb0dac9592cfd0440b66dc5244b1d.camel@perches.com> (raw)
In-Reply-To: <CANiq72m-kvANJsrWHXHoEfRBRbFDt+0nWzma3HxBrBo9tP9Ouw@mail.gmail.com>
On Tue, 2018-08-28 at 17:28 +0200, Miguel Ojeda wrote:
> Hi,
>
> On Tue, Aug 28, 2018 at 3:57 PM, Richard Fitzgerald
> <rf@opensource.cirrus.com> wrote:
> > Reviewed-by: Richard Fitzgerald <rf@opensource.cirrus.com>
> >
> > A maintainer for MAINTAINERS would help avoid these problems, which will
> > tend to happen when changes to the file go through many trees.
> >
>
> A year ago Linus committed 7683e9e52 ("Properly alphabetize
> MAINTAINERS file") which adds scripts/parse-maintainers.pl.
>
> I guess it could just be run once in a while (e.g. before a kernel is
> released, for instance).
And a few patches for parse-maintainers.pl were
added after that.
The latest version also reorders and alphabetizes
the subfields of each section to a preferred order.
So running that latest version would produce quite
a large diff.
That large a diff should only occur once though.
$ perl ./scripts/parse-maintainers.pl --output MAINTAINERS
$ git diff --stat MAINTAINERS
MAINTAINERS | 4014 +++++++++++++++++++++++++++++------------------------------
1 file changed, 2007 insertions(+), 2007 deletions(-)
vs
$ git checkout 7683e9e52 -- scripts/parse-maintainers.pl
$ perl ./scripts/parse-maintainers.pl < MAINTAINERS > MAINTAINERS.new
$ mv MAINTAINERS.new MAINTAINERS
$ git diff --stat MAINTAINERS
MAINTAINERS | 574 ++++++++++++++++++++++++++++++------------------------------
1 file changed, 287 insertions(+), 287 deletions(-)
prev parent reply other threads:[~2018-08-28 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 13:33 Geert Uytterhoeven
2018-08-28 13:57 ` Richard Fitzgerald
2018-08-28 15:28 ` Miguel Ojeda
2018-08-28 18:16 ` 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=b160878ca73bb0dac9592cfd0440b66dc5244b1d.camel@perches.com \
--to=joe@perches.com \
--cc=geert+renesas@glider.be \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rf@opensource.cirrus.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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®