From: Jean Delvare <jdelvare@suse.de>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
Guenter Roeck <linux@roeck-us.net>,
Harry Wei <harryxiyou@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-hwmon@vger.kernel.org, linux-kernel@zh-kernel.org,
Markus Heiser <markus.heiser@darmarit.de>,
Jani Nikula <jani.nikula@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 07/17] SubmitChecklist: rename to RST and add to the development-proccess book
Date: Fri, 16 Sep 2016 10:11:27 +0200 [thread overview]
Message-ID: <20160916101127.77958af9@endymion> (raw)
In-Reply-To: <3955b817eeabc06c9088b4b59722c5e35c175e67.1473893776.git.mchehab@s-opensource.com>
On Wed, 14 Sep 2016 20:05:52 -0300, Mauro Carvalho Chehab wrote:
> Add it to the development-process book, by renaming it to
> SubmitChecklist.rst and move it to the development-process
> directory.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> ---
> .../{SubmitChecklist => development-process/SubmitChecklist.rst} | 2 +-
> Documentation/development-process/index.rst | 1 +
> Documentation/hwmon/submitting-patches | 2 +-
> Documentation/ja_JP/SubmitChecklist | 4 ++--
> Documentation/ja_JP/SubmittingPatches | 2 +-
> Documentation/zh_CN/SubmittingPatches | 2 +-
> 6 files changed, 7 insertions(+), 6 deletions(-)
> rename Documentation/{SubmitChecklist => development-process/SubmitChecklist.rst} (98%)
> (...)
For the hwmon part:
Reviewed-by: Jean Delvare <jdelvare@suse.de>
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2016-09-16 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1473893776.git.mchehab@s-opensource.com>
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 [this message]
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=20160916101127.77958af9@endymion \
--to=jdelvare@suse.de \
--cc=corbet@lwn.net \
--cc=harryxiyou@gmail.com \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kernel@zh-kernel.org \
--cc=linux@roeck-us.net \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@infradead.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.com \
/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