From: Joe Perches <joe@perches.com> To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>, linux-kernel@vger.kernel.org Cc: Linus Torvalds <torvalds@linux-foundation.org>, Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Nathan Chancellor <nathan@kernel.org>, Nick Desaulniers <ndesaulniers@google.com>, linux-riscv@lists.infradead.org, llvm@lists.linux.dev Subject: Re: [PATCH] MAINTAINERS: Sort entries using parse-maintainers.pl Date: Sat, 04 Dec 2021 10:20:24 -0800 [thread overview] Message-ID: <429227f33cf14aee6f0668a3d98aa220b54383d6.camel@perches.com> (raw) In-Reply-To: <20211204175255.1361385-1-j.neuschaefer@gmx.net> 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
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com> To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>, linux-kernel@vger.kernel.org Cc: Linus Torvalds <torvalds@linux-foundation.org>, Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Nathan Chancellor <nathan@kernel.org>, Nick Desaulniers <ndesaulniers@google.com>, linux-riscv@lists.infradead.org, llvm@lists.linux.dev Subject: Re: [PATCH] MAINTAINERS: Sort entries using parse-maintainers.pl Date: Sat, 04 Dec 2021 10:20:24 -0800 [thread overview] Message-ID: <429227f33cf14aee6f0668a3d98aa220b54383d6.camel@perches.com> (raw) In-Reply-To: <20211204175255.1361385-1-j.neuschaefer@gmx.net> 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 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-12-04 18:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-04 17:52 [PATCH] MAINTAINERS: Sort entries using parse-maintainers.pl Jonathan Neuschäfer 2021-12-04 17:52 ` Jonathan Neuschäfer 2021-12-04 18:20 ` Joe Perches [this message] 2021-12-04 18:20 ` Joe Perches 2021-12-04 19:48 ` Jonathan Neuschäfer 2021-12-04 19:48 ` Jonathan Neuschäfer 2021-12-04 22:34 ` Joe Perches 2021-12-04 22:34 ` Joe Perches 2021-12-05 21:04 ` Jonathan Neuschäfer 2021-12-05 21:04 ` Jonathan Neuschäfer
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=429227f33cf14aee6f0668a3d98aa220b54383d6.camel@perches.com \ --to=joe@perches.com \ --cc=aou@eecs.berkeley.edu \ --cc=j.neuschaefer@gmx.net \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=llvm@lists.linux.dev \ --cc=nathan@kernel.org \ --cc=ndesaulniers@google.com \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --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: linkBe 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.