[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YavGALvWdsW+BO9w@latitude>
Date: Sat, 4 Dec 2021 20:48:16 +0100
From: Jonathan Neuschäfer <j.neuschaefer@....net>
To: Joe Perches <joe@...ches.com>
Cc: Jonathan Neuschäfer <j.neuschaefer@....net>,
linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
linux-riscv@...ts.infradead.org, llvm@...ts.linux.dev
Subject: Re: [PATCH] MAINTAINERS: Sort entries using parse-maintainers.pl
On Sat, Dec 04, 2021 at 10:20:24AM -0800, Joe Perches wrote:
> On Sat, 2021-12-04 at 18:52 +0100, Jonathan Neuschäfer wrote:
> > The MAINTAINERS file got slightly out of order again, making it
> > difficult to put new entries at the right (alphabetical) position.
> >
> > Run parse-maintainers.pl to restore the alphabetical order.
> []
> > Checkpatch warns about a few unordered "F:" lines within sections, but I
> > left those alone because I wanted this patch to be as automated as possible.
>
> The --order option does that.
>
> $ ./scripts/parse-maintainers.pl --order --output MAINTAINERS
Ah, good point.
Unfortunately, the result of parse-maintainers.pl --order currently
produces a (small) merge conflict when merged/cherry-picked on top of
-next, so it might be better to start without --order. (Not sure.)
Jonathan
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists