From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Markus Heiser <markus.heiser@darmarit.de>,
Jani Nikula <jani.nikula@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 10/17] email-clients.txt: add it to the development-process book
Date: Wed, 14 Sep 2016 20:05:55 -0300 [thread overview]
Message-ID: <a8d3fda59c538012cedf3570ab5d14bc0a5cc781.1473893776.git.mchehab@s-opensource.com> (raw)
In-Reply-To: <cover.1473893776.git.mchehab@s-opensource.com>
In-Reply-To: <cover.1473893776.git.mchehab@s-opensource.com>
This file is mentioned inside SubmittingPatches, and it is
related to the patch submission process. So, move it to
the right book, making Sphinx build it.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
---
.../{email-clients.txt => development-process/email-clients.rst} | 0
Documentation/development-process/index.rst | 1 +
2 files changed, 1 insertion(+)
rename Documentation/{email-clients.txt => development-process/email-clients.rst} (100%)
diff --git a/Documentation/email-clients.txt b/Documentation/development-process/email-clients.rst
similarity index 100%
rename from Documentation/email-clients.txt
rename to Documentation/development-process/email-clients.rst
diff --git a/Documentation/development-process/index.rst b/Documentation/development-process/index.rst
index 243041af82c3..e38f44729a21 100644
--- a/Documentation/development-process/index.rst
+++ b/Documentation/development-process/index.rst
@@ -18,6 +18,7 @@ Contents:
stable_kernel_rules
kernel-docs
applying-patches
+ email-clients
SubmitChecklist
development-process
--
2.7.4
next prev parent reply other threads:[~2016-09-14 23:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 23:05 [PATCH 00/17] Improve documentation for the development-process Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 01/17] HOWTO.rst: update information about generating documentation Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 02/17] HOWTO.rst: improve some markups to make it visually better Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 03/17] HOWTO.rst: adjust external link references Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 04/17] Changes.rst: add minimal requirements for documentation build Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 05/17] SubmitChecklist: update kernel-doc task Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 06/17] SubmitChecklist: convert it to ReST markup Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 07/17] SubmitChecklist: rename to RST and add to the development-proccess book Mauro Carvalho Chehab
2016-09-16 8:11 ` Jean Delvare
2016-09-14 23:05 ` [PATCH 08/17] doc-rst: add CSS styles for :kbd: and :menuselection: Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 09/17] email-clients.txt: convert it to ReST markup Mauro Carvalho Chehab
2016-09-14 23:05 ` Mauro Carvalho Chehab [this message]
2016-09-14 23:05 ` [PATCH 11/17] SubmittingPatches.rst: Add some cross-references Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 12/17] SubmittingPatches.rst: enrich the Sphinx output Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 13/17] SubmittingDrivers.rst: add a cross reference to CodingStyle Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 14/17] stable_api_nonsense.rst: fix emphasis on Sphinx Mauro Carvalho Chehab
2016-09-14 23:06 ` [PATCH 15/17] ManagementStyle.rst: avoid emphasis where not desired Mauro Carvalho Chehab
2016-09-14 23:06 ` [PATCH 16/17] stable_kernel_rules.rst: Add cross-references to other ReST files Mauro Carvalho Chehab
2016-09-14 23:06 ` [PATCH 17/17] applying-patches.rst: Update the information there Mauro Carvalho Chehab
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=a8d3fda59c538012cedf3570ab5d14bc0a5cc781.1473893776.git.mchehab@s-opensource.com \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@infradead.org \
--cc=mchehab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®