From: Jonathan Corbet <corbet@lwn.net>
To: Alex Shi <alex.shi@linux.alibaba.com>
Cc: Weiwei Jia <harryxiyou@gmail.com>,
linux-doc@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Coly Li <colyli@suse.de>, Fengguang Wu <fengguang.wu@intel.com>,
Li Zefan <lizefan@huawei.com>, Shawn Guo <shawn.guo@linaro.org>,
Li Yang <leoyang.li@nxp.com>
Subject: Re: [PATCH v3 00/31] clean up and reorg Chinese kernel docs
Date: Mon, 11 Mar 2019 08:51:03 -0600 [thread overview]
Message-ID: <20190311085103.566ebac0@lwn.net> (raw)
In-Reply-To: <fb2090f4-5b80-c3f3-5cfa-1115dcd0e1ec@linux.alibaba.com>
On Mon, 11 Mar 2019 14:31:08 +0800
Alex Shi <alex.shi@linux.alibaba.com> wrote:
> What's the normal process of the Chinese kernel doc pick up? Will you
> send a pull request to Corbet? or Corbet pick it them with your comment?
Please repost the series with acks and comments applied - preferably after
the close of the merge window - and I'll apply them then.
Thanks,
jon
prev parent reply other threads:[~2019-03-11 14:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 3:08 [PATCH v3 00/31] clean up and reorg Chinese kernel docs Alex Shi
2019-03-08 3:08 ` [PATCH v3 01/31] docs/zh_CN: add disclaimer file Alex Shi
2019-03-08 3:08 ` [PATCH v3 02/31] docs/zh_CN: move process related docs into process dir Alex Shi
2019-03-08 3:08 ` [PATCH v3 03/31] docs/zh_CN: change Chinese index to know " Alex Shi
2019-03-08 3:08 ` [PATCH v3 04/31] docs/zh_CN: add index file into " Alex Shi
2019-03-08 3:08 ` [PATCH v3 05/31] docs/zh_CN: rename HOWTO into process directory Alex Shi
2019-03-08 3:08 ` [PATCH v3 06/31] docs/zh_CN: howto format changes Alex Shi
2019-03-08 3:08 ` [PATCH v3 07/31] docs/zh_CN: rename SubmittingPatches for html links Alex Shi
2019-03-08 3:08 ` [PATCH v3 08/31] docs/zh_CN: format the submitting-patches doc to rst Alex Shi
2019-03-08 3:08 ` [PATCH v3 09/31] docs/zh_CN: rename stable_kernel_rules doc Alex Shi
2019-03-08 3:08 ` [PATCH v3 10/31] docs/zh_CN: rst format change for stable-kernel-rules Alex Shi
2019-03-08 3:08 ` [PATCH v3 11/31] docs/zh_CN: rename email-clients.txt as email-clients.rst Alex Shi
2019-03-08 3:08 ` [PATCH v3 12/31] docs/zh_CN: do rst format for email-clients.rst Alex Shi
2019-03-08 3:09 ` [PATCH v3 13/31] docs/zh_CN: rename volatile-consider-harmful doc Alex Shi
2019-03-08 3:09 ` [PATCH v3 14/31] docs/zh_CN: volatile doc format changes Alex Shi
2019-03-08 3:09 ` [PATCH v3 15/31] docs/zh_CN: rename SubmittingDrivers Alex Shi
2019-03-08 3:09 ` [PATCH v3 16/31] docs/zh_CN: format submitting drivers as rst Alex Shi
2019-03-08 3:09 ` [PATCH v3 17/31] docs/zh_CN: rename magic-numbers as rst doc Alex Shi
2019-03-08 3:09 ` [PATCH v3 18/31] docs/zh_CN: format the magic-number doc as rst Alex Shi
2019-03-11 2:12 ` [PATCH v3 00/31] clean up and reorg Chinese kernel docs Alex Shi
[not found] ` <CAD+1EGP01hsT_h+XDiyFqon9k4J0rvyYVwdbOQo7qXOmAOmL+g@mail.gmail.com>
[not found] ` <fb2090f4-5b80-c3f3-5cfa-1115dcd0e1ec@linux.alibaba.com>
2019-03-11 14:51 ` Jonathan Corbet [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=20190311085103.566ebac0@lwn.net \
--to=corbet@lwn.net \
--cc=alex.shi@linux.alibaba.com \
--cc=colyli@suse.de \
--cc=fengguang.wu@intel.com \
--cc=harryxiyou@gmail.com \
--cc=leoyang.li@nxp.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=shawn.guo@linaro.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;
as well as URLs for NNTP newsgroup(s).