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+55aFwR+Y+hd8PcGJ+EFsROEekeAiiZ2co5q7-cRwpuVMWSyw@mail.gmail.com>
Date:   Thu, 20 Jul 2017 11:03:31 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Joe Perches <joe@...ches.com>
Cc:     Michael Ellerman <mpe@...erman.id.au>,
        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 Thu, Jul 20, 2017 at 9:48 AM, Joe Perches <joe@...ches.com> wrote:
>
> Same general concept, but then an expectation would be
> relative paths for filename patterns.

No, I actually think we really should require the filename patterns to
be absolute, even if the MAINTAINERS file might be deep in the
hierarchy.

Even if you have some particular driver that it under
"drivers/misc/crazy/random/odd.c", and your MAINTAINERS entry is
somewhere in that drivers hierachy, you might still want to refer to a
documentation file somewhere else, for example.

So file patterns absolutely would need to remain relative to the top
of the repository, not to the location of the MAINTAINERS file.

                     Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ