All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Shi <seakeel@gmail.com>
To: Yanteng Si <siyanteng01@gmail.com>
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <siyanteng@loongson.cn>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/3] docs/zh_CN: Improve zh_CN/process/howto.rst
Date: Thu, 23 Sep 2021 12:04:04 +0800	[thread overview]
Message-ID: <CAJy-AmmDwR71Nno8S-ej3u7Op72Jzf+LHc8Z_HEbW8mW868vgg@mail.gmail.com> (raw)
In-Reply-To: <6790175c0419d5d140f17d9c078c8538136e8190.1631605791.git.siyanteng@loongson.cn>

Reviewed-by: Alex Shi <alexs@kernel.org>

Thanks!

On Tue, Sep 14, 2021 at 4:00 PM Yanteng Si <siyanteng01@gmail.com> wrote:
>
>    - Improve grammar of zh_CN/process/howto.rst.
>    - Resolve potential problems in documentation.
>
> Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
> ---
>  Documentation/translations/zh_CN/process/howto.rst | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/translations/zh_CN/process/howto.rst b/Documentation/translations/zh_CN/process/howto.rst
> index ee3dee476d57..2903d7161bc8 100644
> --- a/Documentation/translations/zh_CN/process/howto.rst
> +++ b/Documentation/translations/zh_CN/process/howto.rst
> @@ -381,7 +381,7 @@ MAINTAINERS文件中可以找到不同话题对应的邮件列表。
>
>  内核社区的工作模式同大多数传统公司开发队伍的工作模式并不相同。下面这些例
>  子,可以帮助你避免某些可能发生问题:
> -用这些话介绍你的修改提案会有好处:
> +用这些话介绍你的修改提案会有好处:(在任何时候你都不应该用中文写提案)
>
>      - 它同时解决了多个问题
>      - 它删除了2000行代码
> @@ -448,8 +448,8 @@ Linux内核社区并不喜欢一下接收大段的代码。修改需要被恰当
>  保证修改分成很多小块,这样在整个项目都准备好被包含进内核之前,其中的一部
>  分可能会先被接收。
>
> -必须了解这样做是不可接受的:试图将未完成的工作提交进内核,然后再找时间修
> -复。
> +你必须明白这么做是无法令人接受的:试图将不完整的代码提交进内核,然后再找
> +时间修复。
>
>
>  证明修改的必要性
> @@ -475,8 +475,8 @@ Linux内核社区并不喜欢一下接收大段的代码。修改需要被恰当
>          https://www.ozlabs.org/~akpm/stuff/tpp.txt
>
>
> -这些事情有时候做起来很难。要在任何方面都做到完美可能需要好几年时间。这是
> -一个持续提高的过程,它需要大量的耐心和决心。只要不放弃,你一定可以做到。
> +这些事情有时候做起来很难。想要在任何方面都做到完美可能需要好几年时间。这
> +是一个持续提高的过程,它需要大量的耐心和决心。只要不放弃,你一定可以做到。
>  很多人已经做到了,而他们都曾经和现在的你站在同样的起点上。
>
>
> --
> 2.27.0
>

  reply	other threads:[~2021-09-23  4:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14  7:59 [PATCH 0/3] docs/zh_CN: improve process translation Yanteng Si
2021-09-14  7:59 ` [PATCH 1/3] docs/zh_CN: Improve zh_CN/process/howto.rst Yanteng Si
2021-09-23  4:04   ` Alex Shi [this message]
2021-09-14  7:59 ` [PATCH 2/3] docs/zh_CN: typo fix and improve translation Yanteng Si
2021-09-23  4:02   ` Alex Shi
2021-09-23  7:00     ` yanteng si
2021-09-14  7:59 ` [PATCH 3/3] docs/zh_CN: modify some words Yanteng Si
2021-09-23  3:52   ` 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=CAJy-AmmDwR71Nno8S-ej3u7Op72Jzf+LHc8Z_HEbW8mW868vgg@mail.gmail.com \
    --to=seakeel@gmail.com \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=siyanteng01@gmail.com \
    --cc=siyanteng@loongson.cn \
    /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.