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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1501211532.5368.42.camel@perches.com>
Date:   Thu, 27 Jul 2017 20:12:12 -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 Thu, 2017-07-27 at 19:43 -0700, Linus Torvalds wrote:
> On Thu, Jul 27, 2017 at 5:30 PM, Joe Perches <joe@...ches.com> wrote:
> > 
> > Maybe add a reordering of the patterns so that each pattern list
> > is in a specific order too
> 
> I don't think this is wrong per se, but I'm not sure I want to get
> into the merge hell any more than we are already.
> 
> Maybe when/if that file is actually split up?

Fine by me.

The get_maintainer patch is a prereq to any split-up.

There are a bunch of little niggly patches that
should go in that remove/update bad F: patterns too
one day.

Given the differences between -next and your tree,
I think only Andrew and quilt would do a decent
job of getting individual patches merged.

Unless you want to take them.

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.