From: Joe Perches <joe@perches.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
llvm@lists.linux.dev
Cc: 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>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v1 1/1] MAINTAINERS: Sort sections with parse-maintainers.pl help
Date: Wed, 17 Nov 2021 15:17:18 -0800 [thread overview]
Message-ID: <dd3b7e0a1b71ab669fc1c0df434bf49eb3dce976.camel@perches.com> (raw)
In-Reply-To: <20211117190553.36144-1-andriy.shevchenko@linux.intel.com>
On Wed, 2021-11-17 at 21:05 +0200, Andy Shevchenko wrote:
> Sort sections with parse-maintainers.pl help since quite a few
> got unsorted from the previous run.
If this is done, I think adding --order to the command line would be better.
For next-20211117 this gives
$ ./scripts/parse-maintainers.pl --input=MAINTAINERS --output=MAINTAINERS --order
$ git diff --stat MAINTAINERS
MAINTAINERS | 826 +++++++++++++++++++++++++++++++++++++++++++++++++++---------------------------------------------------
1 file changed, 413 insertions(+), 413 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
llvm@lists.linux.dev
Cc: 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>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v1 1/1] MAINTAINERS: Sort sections with parse-maintainers.pl help
Date: Wed, 17 Nov 2021 15:17:18 -0800 [thread overview]
Message-ID: <dd3b7e0a1b71ab669fc1c0df434bf49eb3dce976.camel@perches.com> (raw)
In-Reply-To: <20211117190553.36144-1-andriy.shevchenko@linux.intel.com>
On Wed, 2021-11-17 at 21:05 +0200, Andy Shevchenko wrote:
> Sort sections with parse-maintainers.pl help since quite a few
> got unsorted from the previous run.
If this is done, I think adding --order to the command line would be better.
For next-20211117 this gives
$ ./scripts/parse-maintainers.pl --input=MAINTAINERS --output=MAINTAINERS --order
$ git diff --stat MAINTAINERS
MAINTAINERS | 826 +++++++++++++++++++++++++++++++++++++++++++++++++++---------------------------------------------------
1 file changed, 413 insertions(+), 413 deletions(-)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-11-17 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 19:05 [PATCH v1 1/1] MAINTAINERS: Sort sections with parse-maintainers.pl help Andy Shevchenko
2021-11-17 19:05 ` Andy Shevchenko
2021-11-17 23:17 ` Joe Perches [this message]
2021-11-17 23:17 ` Joe Perches
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=dd3b7e0a1b71ab669fc1c0df434bf49eb3dce976.camel@perches.com \
--to=joe@perches.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=aou@eecs.berkeley.edu \
--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: link
Be 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.