From: Jonathan Corbet <corbet@lwn.net>
To: Andy Deng <theandy.deng@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] zh_CN/CodingStyle: Convert to ReST markup
Date: Tue, 24 Jan 2017 16:57:56 -0700 [thread overview]
Message-ID: <20170124165756.7ae7f596@lwn.net> (raw)
In-Reply-To: <20170124235422.8432-1-theandy.deng@gmail.com>
On Wed, 25 Jan 2017 07:54:21 +0800
Andy Deng <theandy.deng@gmail.com> wrote:
> This commit applies all changes from the English version, and should
> be able to work with documentation build system.
>
> Also fixed some translation errors.
So I approve of all of this, to the extent that I can understand it. But
can we split the two above changes into two separate patches, just on
general principles? They are two distinct changes, after all.
Thanks,
jon
next prev parent reply other threads:[~2017-01-24 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 23:54 [PATCH 1/2] zh_CN/CodingStyle: Convert to ReST markup Andy Deng
2017-01-24 23:54 ` [PATCH 2/2] zh_CN/coding-style: Add coding-style into docs build system Andy Deng
2017-01-24 23:57 ` Jonathan Corbet [this message]
2017-01-25 0:28 ` [PATCH 1/2] zh_CN/CodingStyle: Convert to ReST markup Andy Deng
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=20170124165756.7ae7f596@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=theandy.deng@gmail.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