From: Brian Norris <computersforpeace@gmail.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org
Subject: [PATCH (mtd-www) 2/3] source: update patch title format
Date: Fri, 4 May 2012 21:04:59 -0700 [thread overview]
Message-ID: <1336190700-27345-2-git-send-email-computersforpeace@gmail.com> (raw)
In-Reply-To: <1336190700-27345-1-git-send-email-computersforpeace@gmail.com>
Today, patches usually use "mtd: target: ..." (in lowercase) rather than
"[MTD] TARGET: ..."
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
---
source.xml | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/source.xml b/source.xml
index faba4a1..01c359f 100644
--- a/source.xml
+++ b/source.xml
@@ -66,10 +66,10 @@ simple rules should be followed when submitting patches</p>
<ol>
<li>Provide a short summary line of the patch in the format:</li><br />
-<code>[PATCH] [MTD] DETAILEDTARGET: short summary</code>
+<code>[PATCH] mtd: DETAILEDTARGET: short summary</code>
<p>
-DETAILEDTARGET should be one of the MTD subcomponents, e.g. NAND, CHIPS,
-MAPS, CORE, and/or a filename if it simplifies the review/recognition of
+DETAILEDTARGET should be one of the MTD subcomponents, e.g. nand, chips,
+maps, core, and/or a filename if it simplifies the review/recognition of
patch relevance.</p>
<li>Empty new line</li>
--
1.7.5.4.2.g519b1
next prev parent reply other threads:[~2012-05-05 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 4:04 [PATCH (mtd-www) 1/3] doc: update info for Linux 3.0 Brian Norris
2012-05-05 4:04 ` Brian Norris [this message]
2012-05-05 4:05 ` [PATCH (mtd-www) 3/3] faq: ubifs: fix grammar, spelling Brian Norris
2012-05-05 9:53 ` [PATCH (mtd-www) 1/3] doc: update info for Linux 3.0 Artem Bityutskiy
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=1336190700-27345-2-git-send-email-computersforpeace@gmail.com \
--to=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.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.