From: Hu Haowen <src.res.211@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 0/6] docs/zh_TW: update zh_TW's documentation from an ascensive aspect
Date: Mon, 24 Jul 2023 18:32:53 +0800 [thread overview]
Message-ID: <8c8c02c2-0aee-af91-deda-bdfea325477d@gmail.com> (raw)
In-Reply-To: <87bkg5dp6x.fsf@meer.lwn.net>
On 2023/7/22 03:44, Jonathan Corbet wrote:
> Hu Haowen <src.res.211@gmail.com> writes:
>
>> Update zh_TW's documentation concentrating on the following aspects:
>>
>> * The file tree structure changes of the main documentation;
>> * Some changes and ideas from zh_CN translation;
>> * Removal for several obsoleted contents within the zh_TW translation
>> or those which are not exising anymore in the main documentation.
>> * Replacements for some incorrect words and phrases in traditional
>> Chinese or those which are odd within their context being hard for
>> readers to comprehend.
>>
>> Hu Haowen (6):
>> docs/zh_TW: update admin-guide
>> docs/zh_TW: update arch
>> docs/zh_TW: update cpu-freq
>> docs/zh_TW: update filesystems
>> docs/zh_TW: update process
>> docs/zh_TW: turn zh_CN's folder references and headers into zh_TW's
>> ones
>
> So b4 doesn't like this one:
>
>> WARNING: Message contains suspicious unicode control characters!
>> Subject: [PATCH RESEND 5/6] docs/zh_TW: update process
>> Line: +.. SPDX-License-Identifier: GPL-2.0
>> -------^
>> Char: ZERO WIDTH NO-BREAK SPACE (0xfeff)
>> If you are sure about this, rerun with the right flag to allow.
>> AM FAILED
>>
>
> Could you resend, please, without the funky control characters?
>
Fixed in patch v2:
https://lore.kernel.org/lkml/20230724041715.20050-1-src.res.211@gmail.com/
Thanks,
Hu Haowen
> Thanks,
>
> jon
prev parent reply other threads:[~2023-07-24 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 13:27 [PATCH RESEND 0/6] docs/zh_TW: update zh_TW's documentation from an ascensive aspect Hu Haowen
2023-07-20 13:27 ` [PATCH RESEND 1/6] docs/zh_TW: update admin-guide Hu Haowen
2023-07-20 13:27 ` [PATCH RESEND 2/6] docs/zh_TW: update arch Hu Haowen
2023-07-20 13:27 ` [PATCH RESEND 3/6] docs/zh_TW: update cpu-freq Hu Haowen
2023-07-20 13:27 ` [PATCH RESEND 4/6] docs/zh_TW: update filesystems Hu Haowen
2023-07-20 13:27 ` [PATCH RESEND 5/6] docs/zh_TW: update process Hu Haowen
2023-07-20 13:27 ` [PATCH RESEND 6/6] docs/zh_TW: turn zh_CN's folder references and headers into zh_TW's ones Hu Haowen
2023-07-20 13:55 ` [PATCH RESEND 0/6] docs/zh_TW: update zh_TW's documentation from an ascensive aspect Jonathan Corbet
2023-07-20 15:30 ` Hu Haowen
2023-07-20 15:51 ` Jonathan Corbet
2023-07-21 19:44 ` Jonathan Corbet
2023-07-24 10:32 ` Hu Haowen [this message]
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=8c8c02c2-0aee-af91-deda-bdfea325477d@gmail.com \
--to=src.res.211@gmail.com \
--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