From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pz0-f43.google.com ([209.85.210.43]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1SQWFE-0003bA-8P for linux-mtd@lists.infradead.org; Sat, 05 May 2012 04:05:20 +0000 Received: by mail-pz0-f43.google.com with SMTP id z8so5059468daj.30 for ; Fri, 04 May 2012 21:05:20 -0700 (PDT) From: Brian Norris To: Artem Bityutskiy Subject: [PATCH (mtd-www) 2/3] source: update patch title format Date: Fri, 4 May 2012 21:04:59 -0700 Message-Id: <1336190700-27345-2-git-send-email-computersforpeace@gmail.com> In-Reply-To: <1336190700-27345-1-git-send-email-computersforpeace@gmail.com> References: <1336190700-27345-1-git-send-email-computersforpeace@gmail.com> Cc: Brian Norris , linux-mtd@lists.infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Today, patches usually use "mtd: target: ..." (in lowercase) rather than "[MTD] TARGET: ..." Signed-off-by: Brian Norris --- 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

  1. Provide a short summary line of the patch in the format:

  2. -[PATCH] [MTD] DETAILEDTARGET: short summary +[PATCH] mtd: DETAILEDTARGET: short summary

    -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.

  3. Empty new line
  4. -- 1.7.5.4.2.g519b1