linux-kernel - Re: [PATCH RESEND v4] MAINTAINERS: fix lots of alphabetic ordering

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: <CA+55aFx1fe1yBj1-ioEPtkMAvFSvs8PhzM3w8NpbM7P3KeZdsg@mail.gmail.com>
Date:   Wed, 19 Jul 2017 21:24:13 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Joe Perches <joe@...ches.com>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Randy Dunlap <rdunlap@...radead.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RESEND v4] MAINTAINERS: fix lots of alphabetic ordering

On Wed, Jul 19, 2017 at 6:05 PM, Joe Perches <joe@...ches.com> wrote:
>
> Just for ease of manipulation and not breaking the script much,
> I'd suggest just having a MAINTAINERS directory and stuffing
> each of the sections into separate files.
>
> The script would only need to add $ cat MAINTAINERS/* as input.

So I don't mind the idea of just making MAINTAINERS a directory, but I
don't think we want to so far as to make one file per entry. That's
what, 1500+ files tiny files or so? Seems a bit excessive.

Maybe we can just do the prefix thing and just do 26 files A-Z
instead? Or maybe go by first word (so all the ARM things would go in
one place?)

A couple of hundred files sounds fine. A couple of thousand files
sound a bit excessive..

             Linus