From: Hu Haowen <src.res@email.cn>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 3/4] docs/zh_TW: fix an issue while building
Date: Sat, 3 Jul 2021 22:31:29 +0800 [thread overview]
Message-ID: <20210703143130.18349-3-src.res@email.cn> (raw)
In-Reply-To: <20210703143130.18349-1-src.res@email.cn>
When building the documentation, the following issue was reported:
/home/src-resources/Coding/Projects/Other-Projects/Linux/Documentation/
translations/zh_TW/admin-guide/reporting-issues.rst:712: WARNING:
duplicate label translations/zh_tw/admin-guide/reporting-issues:
檢查「汙染」標誌, other instance in /home/src-resources/Coding/Projects/
Other-Projects/Linux/Documentation/translations/zh_TW/admin-guide/
reporting-issues.rst
Consequently, replace "檢查「汙染」標誌" with "檢測「汙染」標誌" to
solve it.
Signed-off-by: Hu Haowen <src.res@email.cn>
---
.../translations/zh_TW/admin-guide/reporting-issues.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/translations/zh_TW/admin-guide/reporting-issues.rst b/Documentation/translations/zh_TW/admin-guide/reporting-issues.rst
index 390a1f40ba2f..27638e199f13 100644
--- a/Documentation/translations/zh_TW/admin-guide/reporting-issues.rst
+++ b/Documentation/translations/zh_TW/admin-guide/reporting-issues.rst
@@ -371,7 +371,7 @@ Linux內核破壞了它處理的數據或損壞了它運行的硬體。當內核
內核模塊。
-檢查「汙染」標誌
+檢測「汙染」標誌
----------------
*當問題發生時，檢查您的內核是否被「汙染」，因爲使內核設置這個標誌的事件可
--
2.25.1
next parent reply other threads:[~2021-07-03 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210703143130.18349-1-src.res@email.cn>
2021-07-03 14:31 ` Hu Haowen [this message]
2021-07-12 17:10 ` [PATCH v3 3/4] docs/zh_TW: fix an issue while building Jonathan Corbet
2021-07-14 3:57 ` Hu Haowen
2021-07-03 14:31 ` [PATCH v3 4/4] docs/zh_TW: add SPDX-License-Identifiers for translations in zh_TW/process Hu Haowen
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=20210703143130.18349-3-src.res@email.cn \
--to=src.res@email.cn \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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 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).