From: Alex Shi <alex.shi@linux.alibaba.com>
To: Wu XiangCheng <bobwxc@email.cn>
Cc: harryxiyou@gmail.com, corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 1/9] docs/zh_CN: Improve zh_CN/process/index.rst
Date: Mon, 1 Mar 2021 16:37:41 +0800 [thread overview]
Message-ID: <4cbfdc6e-1fca-fa12-e169-14f9b74c7039@linux.alibaba.com> (raw)
In-Reply-To: <bf7d8e474ea3332a8595f46619b427b1ebbcb791.1614488009.git.bobwxc@email.cn>
Reviewed-by: Alex Shi <alex.shi@linux.alibaba.com>
在 2021/2/28 下午1:37, Wu XiangCheng 写道:
> Improve language and grammar of zh_CN/process/index.rst
>
> Signed-off-by: Wu XiangCheng <bobwxc@email.cn>
> ---
> Documentation/translations/zh_CN/process/index.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/translations/zh_CN/process/index.rst b/Documentation/translations/zh_CN/process/index.rst
> index 8051a7b322c5..39e9c88fbaa6 100644
> --- a/Documentation/translations/zh_CN/process/index.rst
> +++ b/Documentation/translations/zh_CN/process/index.rst
> @@ -13,11 +13,11 @@
> 与Linux 内核社区一起工作
> ========================
>
> -那么你想成为Linux内核开发人员？ 欢迎！ 不但从技术意义上讲有很多关于内核的知识
> -需要学，而且了解我们社区的工作方式也很重要。 阅读这些文章可以让您以更轻松地,
> -麻烦最少的方式将更改合并到内核。
> +你想成为Linux内核开发人员吗？欢迎之至！在学习许多关于内核的技术知识的同时，
> +了解我们社区的工作方式也很重要。阅读这些文档可以让您以更轻松的、麻烦更少的
> +方式将更改合并到内核。
>
> -以下是每位开发人员应阅读的基本指南。
> +以下是每位开发人员都应阅读的基本指南：
>
> .. toctree::
> :maxdepth: 1
> @@ -47,7 +47,7 @@
> management-style
> embargoed-hardware-issues
>
> -这些是一些总体技术指南，由于缺乏更好的地方，现在已经放在这里
> +这些是一些总体性技术指南，由于不大好分类而放在这里：
>
> .. toctree::
> :maxdepth: 1
>
next prev parent reply other threads:[~2021-03-01 8:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 5:37 [PATCH v2 0/9] docs/zh_CN: Improve language in zh_CN/process/ Wu XiangCheng
2021-02-28 5:37 ` [PATCH v2 1/9] docs/zh_CN: Improve zh_CN/process/index.rst Wu XiangCheng
2021-03-01 8:37 ` Alex Shi [this message]
2021-02-28 5:38 ` [PATCH v2 2/9] docs/zh_CN: Improve zh_CN/process/1.Intro.rst Wu XiangCheng
2021-03-01 8:38 ` Alex Shi
2021-02-28 5:38 ` [PATCH v2 3/9] docs/zh_CN: Improve zh_CN/process/2.Process.rst Wu XiangCheng
2021-03-01 8:39 ` Alex Shi
2021-02-28 5:38 ` [PATCH v2 4/9] docs/zh_CN: Improve zh_CN/process/3.Early-stage.rst Wu XiangCheng
2021-03-01 9:13 ` Alex Shi
2021-03-03 15:34 ` Wu X.C.
2021-03-04 7:03 ` Alex Shi
2021-02-28 5:39 ` [PATCH v2 5/9] docs/zh_CN: Improve zh_CN/process/4.Coding.rst Wu XiangCheng
2021-02-28 5:39 ` [PATCH v2 6/9] docs/zh_CN: Improve zh_CN/process/5.Posting.rst Wu XiangCheng
2021-02-28 5:40 ` [PATCH v2 7/9] docs/zh_CN: Improve zh_CN/process/6.Followthrough Wu XiangCheng
2021-03-04 7:23 ` Alex Shi
2021-03-04 7:40 ` Wu X.C.
2021-03-04 8:05 ` Alex Shi
2021-02-28 5:40 ` [PATCH v2 8/9] docs/zh_CN: Improve zh_CN/process/7.AdvancedTopics Wu XiangCheng
2021-02-28 5:40 ` [PATCH v2 9/9] docs/zh_CN: Improve zh_CN/process/8.Conclusion.rst Wu XiangCheng
2021-03-01 8:37 ` [PATCH v2 0/9] docs/zh_CN: Improve language in zh_CN/process/ Alex Shi
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=4cbfdc6e-1fca-fa12-e169-14f9b74c7039@linux.alibaba.com \
--to=alex.shi@linux.alibaba.com \
--cc=bobwxc@email.cn \
--cc=corbet@lwn.net \
--cc=harryxiyou@gmail.com \
--cc=linux-doc@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.