netdev - Re: [PATCH] MAINTAINERS: correct entries for ISDN/mISDN section

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: <alpine.DEB.2.21.2002040550540.3062@felia>
Date:   Tue, 4 Feb 2020 06:08:37 +0100 (CET)
From:   Lukas Bulwahn <lukas.bulwahn@...il.com>
To:     Andy Shevchenko <andy.shevchenko@...il.com>
cc:     Joe Perches <joe@...ches.com>, Jakub Kicinski <kuba@...nel.org>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>,
        Karsten Keil <isdn@...ux-pingi.de>,
        Arnd Bergmann <arnd@...db.de>,
        isdn4linux@...tserv.isdn4linux.de, netdev <netdev@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: correct entries for ISDN/mISDN section

On Mon, 3 Feb 2020, Andy Shevchenko wrote:

> On Mon, Feb 3, 2020 at 1:08 PM Joe Perches <joe@...ches.com> wrote:
> > On Mon, 2020-02-03 at 12:13 +0200, Andy Shevchenko wrote:
> > > On Sun, Feb 2, 2020 at 10:45 PM Jakub Kicinski <kuba@...nel.org> wrote:
> 
> ...
> 
> > > I'm not sure it's ready. I think parse-maintainers.pl will change few
> > > lines here.
> >
> > parse-maintainers would change a _lot_ of the MAINTAINERS file
> > by reordering section letters.
> 
> I think it's quite easy to find out if it had changed the record in question.
>

I checked it and it does change a bit. My patch adds to a list of file 
entries sorted by "relevance" (not alphabetically) two further minor (by 
relevance) entries, i.e., Kconfig and Makefile, to the end of that list.

The other reorderings would have already applied to the original state; 
rather than trying to "fix" this locally for this one patch here, I would 
prefer to understand why the discussion on splitting the MAINTAINERS file,
summarized at https://lwn.net/Articles/730509/, got stuck and how I can 
contribute to that. If that bigger change would happen, we could 
automatically clean up all the entries when the things are splitted, 
rather than sending reordering patches to the maintainers that then spend 
time on trying to merge that all back together.

Lukas