From: Jonathan Corbet <corbet@lwn.net>
To: Hu Haowen <src.res@email.cn>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/4] docs/zh_TW: fix an issue while building
Date: Mon, 12 Jul 2021 11:10:50 -0600 [thread overview]
Message-ID: <87r1g3pied.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210703143130.18349-3-src.res@email.cn>
Hu Haowen <src.res@email.cn> writes:
> 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>
Please, just update the original patch to not introduce the error in the
first place. While you are at it, add the SPDX headers when you first
add the files rather than fixing it up afterward.
This is a vast amount of material that I am absolutely incapable of
making any sort of informed decision on. Is there any chance that
somebody can review this work?
Thanks,
jon
next prev parent reply other threads:[~2021-07-12 17:10 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 ` [PATCH v3 3/4] docs/zh_TW: fix an issue while building Hu Haowen
2021-07-12 17:10 ` Jonathan Corbet [this message]
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=87r1g3pied.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=src.res@email.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 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).