| 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: <20121002121443.GT4587@mwanda> Date: Tue, 2 Oct 2012 15:14:43 +0300 From: Dan Carpenter <dan.carpenter@...cle.com> To: Peter Senna Tschudin <peter.senna@...il.com> Cc: joe@...ches.com, gregkh@...uxfoundation.org, davem@...emloft.net, arnd@...db.de, elezegarcia@...il.com, Julia.Lawall@...6.fr, linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org Subject: Re: [PATCH RFC] MAINTAINERS: Add section for subsystem shortname On Tue, Oct 02, 2012 at 01:57:04PM +0200, Peter Senna Tschudin wrote: > The shortname for a subsystem, that is primarly used when sending patches over E-mail, is not stored anywhere in the source code. Actually one need to dig git log or mailing list archives. There is no standard, and the Maintainer choose how to short name his/her subsystem. MAINTAINERS file is the right place for storing this information. > > U is the second letter of Subsystem. > > This will also enable automatic tools like scripts/get_maintainer.pl to provide the correct short name for each filename in the Kernel source tree. > This is pretty useless without a script to parse it. Also none of subsystem names you chose as examples are correct. Please line wrap your commit message at 72 characters. regards, dan carpenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists