Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <8c8c02c2-0aee-af91-deda-bdfea325477d@gmail.com>
Date:   Mon, 24 Jul 2023 18:32:53 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.13.0
Subject: Re: [PATCH RESEND 0/6] docs/zh_TW: update zh_TW's documentation from
 an ascensive aspect
To:     Jonathan Corbet <corbet@lwn.net>
Cc:     linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
References: <20230720132729.1821-1-src.res.211@gmail.com>
 <87bkg5dp6x.fsf@meer.lwn.net>
Content-Language: en-US
From:   Hu Haowen <src.res.211@gmail.com>
In-Reply-To: <87bkg5dp6x.fsf@meer.lwn.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk


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