linux-kernel - Re: [PATCH] MAINTAINERS: Sort entries using parse-maintainers.pl

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2ced60214ef3bf449e27f5cb22d3dbd0863d97bb.camel@perches.com>
Date:   Sat, 04 Dec 2021 14:34:36 -0800
From:   Joe Perches <joe@...ches.com>
To:     Jonathan Neuschäfer <j.neuschaefer@....net>
Cc:     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, 2021-12-04 at 20:48 +0100, Jonathan Neuschäfer wrote:
> 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.)

My preference is still to automate the running of this command
by some script and apply it just before every -rc1 is released.