From: Yanteng Si <si.yanteng@linux.dev>
To: Dongliang Mu <dzm91@hust.edu.cn>, Alex Shi <alexs@kernel.org>,
Jonathan Corbet <corbet@lwn.net>, SeongJae Park <sj@kernel.org>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Thorsten Blum <thorsten.blum@toblux.com>
Cc: hust-os-kernel-patches@googlegroups.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs/zh_CN: update the translation of process/coding-style.rst
Date: Fri, 18 Oct 2024 15:09:54 +0800 [thread overview]
Message-ID: <521e45c9-a402-4c53-936b-6052fa23c052@linux.dev> (raw)
In-Reply-To: <20241018014609.3781089-1-dzm91@hust.edu.cn>
在 2024/10/18 09:46, Dongliang Mu 写道:
> Update to commit c5d436f05a3f ("docs/process: fix typos")
>
> scripts/checktransupdate.py reports:
>
> Documentation/translations/zh_CN/process/coding-style.rst
> commit c5d436f05a3f ("docs/process: fix typos")
> commit 82b8000c28b5 ("net: drop special comment style")
> 2 commits needs resolving in total
>
> Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
Reviewed-by: Yanteng Si <si.yanteng@linux.dev>
Thanks,
Yanteng
> ---
> v1->v2: revise the script name
> .../translations/zh_CN/process/coding-style.rst | 11 -----------
> 1 file changed, 11 deletions(-)
>
> diff --git a/Documentation/translations/zh_CN/process/coding-style.rst b/Documentation/translations/zh_CN/process/coding-style.rst
> index 10b9cb4f6a65..0484d0c65c25 100644
> --- a/Documentation/translations/zh_CN/process/coding-style.rst
> +++ b/Documentation/translations/zh_CN/process/coding-style.rst
> @@ -560,17 +560,6 @@ Documentation/translations/zh_CN/doc-guide/index.rst 和 scripts/kernel-doc 。
> * with beginning and ending almost-blank lines.
> */
>
> -对于在 net/ 和 drivers/net/ 的文件,首选的长 (多行) 注释风格有些不同。
> -
> -.. code-block:: c
> -
> - /* The preferred comment style for files in net/ and drivers/net
> - * looks like this.
> - *
> - * It is nearly the same as the generally preferred comment style,
> - * but there is no initial almost-blank line.
> - */
> -
> 注释数据也是很重要的,不管是基本类型还是衍生类型。为了方便实现这一点,每一行
> 应只声明一个数据 (不要使用逗号来一次声明多个数据)。这样你就有空间来为每个数据
> 写一段小注释来解释它们的用途了。
next prev parent reply other threads:[~2024-10-18 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 1:46 [PATCH v2] docs/zh_CN: update the translation of process/coding-style.rst Dongliang Mu
2024-10-18 7:09 ` Yanteng Si [this message]
2024-10-21 15:41 ` Jonathan Corbet
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=521e45c9-a402-4c53-936b-6052fa23c052@linux.dev \
--to=si.yanteng@linux.dev \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=federico.vaga@vaga.pv.it \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj@kernel.org \
--cc=thorsten.blum@toblux.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