| 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
| ||
|
Message-ID: <f53fdf2283e1c847a4c44ea7bea4cb6600c06991.camel@perches.com>
Date: Sun, 29 Mar 2020 19:35:22 -0700
From: Joe Perches <joe@...ches.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: re: commit 23cb8490c0d3 ("MAINTAINERS: fix bad file pattern")
MAINTAINERS: fix bad file pattern
Testing 'parse-maintainers' due to the previous commit shows a bad file
pattern for the "TI VPE/CAL DRIVERS" entry in the MAINTAINERS file.
There's also a lot of mis-ordered entries, but I'm still a bit nervous
about the inevitable and annoying merge problems it would probably cause
to fix them up.
The MAINTAINERS file is one of my least favorite files due to being huge
and centralized, but fixing it is also horribly painful for that reason.
The identical commit was sent at least twice.
Once directly to you.
https://patchwork.kernel.org/patch/11361131/
https://lore.kernel.org/linux-media/20200128145828.74161-1-andriy.shevchenko@linux.intel.com/
About the pain associated to fixing the file:
I think it would be minimally painful to run
$ ./scripts/parse-maintainers.pl --input=MAINTAINERS --output=MAINTAINERS --order
Immediately before an -rc1 is released.
Relatively few of any pending patches to MAINTAINERS
in -next would be impacted and there would be better
consistency in the silly file.
Powered by blists - more mailing lists