On Tue, 2018-08-28 at 17:28 +0200, Miguel Ojeda wrote:
> Hi,
>
> On Tue, Aug 28, 2018 at 3:57 PM, Richard Fitzgerald
> <r...@opensource.cirrus.com> wrote:
> > Reviewed-by: Richard Fitzgerald <r...@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(-)
