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+55aFxXsxUfxVj=arMk65s4k9Om6_sPnfKAyN3gY5FzX21S9Q@mail.gmail.com>
Date:   Wed, 2 Aug 2017 11:15:09 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Joe Perches <joe@...ches.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2] get_maintainer: Prepare for separate MAINTAINERS files

On Wed, Aug 2, 2017 at 11:06 AM, Randy Dunlap <rdunlap@...radead.org> wrote:
>
> IMO, the parse-maintainters.pl (sorting) script makes the need for separate
> MAINTAINERS files much less important since the file can be "fixed" easily
> at any time.

For me it's not the "fixing". It's the inevitable merge mess, and the
two hundred commits that I have to go through.

That said, the extra time just to look for MAINTAINERS files makes me
unhappy. It may be just .3s on Joe's machine, but it's presumably much
more when things aren't in the filesystem caches. I (like apparently
Joe) have an SSD so it's not a big deal for me, but..

Just having a single MAINTAINERS directory would alleviate that concern.

             Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ