From: "Wu X.C." <bobwxc@email.cn>
To: Alex Shi <seakeel@gmail.com>
Cc: Alex Shi <alexs@kernel.org>,
Alex Shi <alex.shi@linux.alibaba.com>,
Jonathan Corbet <corbet@lwn.net>,
YanTeng Si <sterlingteng@gmail.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 5/8] docs/zh_CN: Add translation zh_CN/doc-guide/contributing.rst
Date: Tue, 13 Apr 2021 13:17:07 +0800 [thread overview]
Message-ID: <20210413051707.GA19405@bobwxc.top> (raw)
In-Reply-To: <09477ecd-4964-01a1-b521-308aaa1ceda0@gmail.com>
On Tue, Apr 13, 2021 at 01:10:56PM +0800, Alex Shi wrote:
>
>
> On 2021/4/7 下午3:51, Wu XiangCheng wrote:
> > +C代码编译器发出的警告常常会被视为误报，从而导致旨在让编译器闭嘴的补丁。文档
> > +构建中的警告几乎总是指向真正的问题；要消除这些警告，需要理解问题并从源头上
> > +解决问题。因此，修复文档警告的补丁不应在标题中直接写“修复警告”；它们应该指明
>
> Since all the patches are write in English, we'd better to keep
> 'fix a warning' in English, or give a extra comment here.
Use “fix a warning(修复警告)”
Thanks!
>
> Thanks!
>
> > +真正修复的问题。
next prev parent reply other threads:[~2021-04-13 5:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 7:50 [PATCH v3 0/8] docs/zh_CN: Add translations in zh_CN/doc-guide/ Wu XiangCheng
2021-04-07 7:50 ` [PATCH v3 1/8] docs/zh_CN: Add translation zh_CN/doc-guide/sphinx.rst Wu XiangCheng
2021-04-13 4:42 ` Alex Shi
2021-04-13 5:08 ` Wu X.C.
2021-04-07 7:50 ` [PATCH v3 2/8] docs/zh_CN: Add two image example files Wu XiangCheng
2021-04-13 4:51 ` Alex Shi
2021-04-13 4:57 ` Wu X.C.
2021-04-07 7:50 ` [PATCH v3 3/8] docs/zh_CN: Add translation zh_CN/doc-guide/kernel-doc.rst Wu XiangCheng
2021-04-07 7:51 ` [PATCH v3 4/8] docs/zh_CN: Add translation zh_CN/doc-guide/parse-headers.rst Wu XiangCheng
2021-04-12 16:12 ` teng sterling
2021-04-13 5:34 ` Wu X.C.
2021-04-13 6:18 ` Alex Shi
2021-04-13 6:35 ` Wu X.C.
2021-04-13 10:00 ` teng sterling
2021-04-13 5:03 ` Alex Shi
2021-04-07 7:51 ` [PATCH v3 5/8] docs/zh_CN: Add translation zh_CN/doc-guide/contributing.rst Wu XiangCheng
2021-04-07 9:30 ` teng sterling
2021-04-07 9:54 ` Wu X.C.
2021-04-07 15:00 ` teng sterling
2021-04-07 15:22 ` Wu X.C.
2021-04-08 3:23 ` teng sterling
2021-04-08 14:10 ` [PATCH v4 " Wu XiangCheng
2021-04-08 16:59 ` Jonathan Corbet
2021-04-12 12:28 ` Wu X.C.
2021-04-13 5:10 ` [PATCH v3 " Alex Shi
2021-04-13 5:17 ` Wu X.C. [this message]
2021-04-07 7:51 ` [PATCH v3 6/8] docs/zh_CN: Add translation zh_CN/doc-guide/maintainer-profile.rst Wu XiangCheng
2021-04-07 8:28 ` teng sterling
2021-04-07 9:18 ` Wu X.C.
2021-04-07 14:47 ` teng sterling
2021-04-07 7:51 ` [PATCH v3 7/8] docs/zh_CN: Add translation zh_CN/doc-guide/index.rst Wu XiangCheng
2021-04-07 7:52 ` [PATCH v3 8/8] docs/zh_CN: Link zh_CN/doc-guide to zh_CN/index.rst Wu XiangCheng
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=20210413051707.GA19405@bobwxc.top \
--to=bobwxc@email.cn \
--cc=alex.shi@linux.alibaba.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=seakeel@gmail.com \
--cc=sterlingteng@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;
as well as URLs for NNTP newsgroup(s).