From: Peter Senna Tschudin <peter.senna@gmail.com>
To: joe@perches.com
Cc: gregkh@linuxfoundation.org, davem@davemloft.net, arnd@arndb.de,
elezegarcia@gmail.com, dan.carpenter@oracle.com,
Julia.Lawall@lip6.fr, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org,
Peter Senna Tschudin <peter.senna@gmail.com>
Subject: [PATCH RFC] MAINTAINERS: Add section for subsystem shortname
Date: Tue, 02 Oct 2012 11:57:04 +0000 [thread overview]
Message-ID: <1349179024-5319-1-git-send-email-peter.senna@gmail.com> (raw)
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.
Signed-off-by: Peter Senna Tschudin <peter.senna@gmail.com>
---
MAINTAINERS | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3386238..a1be2a1 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -104,6 +104,11 @@ Descriptions of section entries:
matches patches or files that contain one or more of the words
printk, pr_info or pr_err
One regex pattern per line. Multiple K: lines acceptable.
+ U: Subsystem short name. Used in the subject of patch sent by email to
+ identify that subsystem. Short means up to 20 chars. Examples:
+ U: media
+ U: media/em28xx
+ U: SCSI
Note: For the hard of thinking, this list is meant to remain in alphabetical
order. If you could add yourselves to it in alphabetical order that would be
--
1.7.11.4
WARNING: multiple messages have this Message-ID (diff)
From: Peter Senna Tschudin <peter.senna@gmail.com>
To: joe@perches.com
Cc: gregkh@linuxfoundation.org, davem@davemloft.net, arnd@arndb.de,
elezegarcia@gmail.com, dan.carpenter@oracle.com,
Julia.Lawall@lip6.fr, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org,
Peter Senna Tschudin <peter.senna@gmail.com>
Subject: [PATCH RFC] MAINTAINERS: Add section for subsystem shortname
Date: Tue, 2 Oct 2012 13:57:04 +0200 [thread overview]
Message-ID: <1349179024-5319-1-git-send-email-peter.senna@gmail.com> (raw)
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.
Signed-off-by: Peter Senna Tschudin <peter.senna@gmail.com>
---
MAINTAINERS | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3386238..a1be2a1 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -104,6 +104,11 @@ Descriptions of section entries:
matches patches or files that contain one or more of the words
printk, pr_info or pr_err
One regex pattern per line. Multiple K: lines acceptable.
+ U: Subsystem short name. Used in the subject of patch sent by email to
+ identify that subsystem. Short means up to 20 chars. Examples:
+ U: media
+ U: media/em28xx
+ U: SCSI
Note: For the hard of thinking, this list is meant to remain in alphabetical
order. If you could add yourselves to it in alphabetical order that would be
--
1.7.11.4
next reply other threads:[~2012-10-02 11:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 11:57 Peter Senna Tschudin [this message]
2012-10-02 11:57 ` [PATCH RFC] MAINTAINERS: Add section for subsystem shortname Peter Senna Tschudin
2012-10-02 12:14 ` Dan Carpenter
2012-10-02 12:14 ` Dan Carpenter
2012-10-02 12:33 ` Peter Senna Tschudin
2012-10-02 12:33 ` Peter Senna Tschudin
2012-10-02 12:40 ` Ezequiel Garcia
2012-10-02 12:40 ` Ezequiel Garcia
2012-10-02 12:53 ` Peter Senna Tschudin
2012-10-02 12:53 ` Peter Senna Tschudin
2012-10-02 13:08 ` Ezequiel Garcia
2012-10-02 13:08 ` Ezequiel Garcia
2012-10-02 13:13 ` Peter Senna Tschudin
2012-10-02 13:13 ` Peter Senna Tschudin
2012-10-02 13:48 ` Joe Perches
2012-10-02 13:48 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1349179024-5319-1-git-send-email-peter.senna@gmail.com \
--to=peter.senna@gmail.com \
--cc=Julia.Lawall@lip6.fr \
--cc=arnd@arndb.de \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=elezegarcia@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.