linux-kernel - Re: [PATCH Y.A. RESEND] MAINTAINERS: fix alpha. 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] [day] [month] [year] [list]

Date:   Sat, 29 Jul 2017 10:46:43 -0700
From:   Joe Perches <joe@...ches.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Randy Dunlap <rdunlap@...radead.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH Y.A. RESEND] MAINTAINERS: fix alpha. ordering

On Fri, 2017-07-28 at 15:30 -0700, Linus Torvalds wrote:
> On Thu, Jul 27, 2017 at 8:12 PM, Joe Perches <joe@...ches.com> wrote:
> > 
> > I think it's better to centralize the MAINTAINERS
> > location in <tree>/MAINTAINERS/<files> than spread
> > them all over the tree given how many subsystems and
> > maintainerships are also spread around the tree.
> > 
> > But the get_maintainers patch I sent allows both
> > styles.
> 
> Possibly. I just did realize that we have one de-centralized
> maintainers file out there already, and have had for 3+ years:
> drivers/staging/unisys/MAINTAINERS.

That file should be deleted as it's duplicated
in the standard MAINTAINERS file

> One thing I like about the decentralized model is that it looks like
> we could automate the initial split fairly well based on F: patterns.
> Something like:
> 
>  - if we have a single F-pattern line, without directory wildcards,
> put the entry in the MAINTAINERS directory for that F-pattern

That would create more than 750 files.