From: Jonathan Corbet <corbet@lwn.net>
To: Hu Haowen <src.res.211@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] docs/zh_TW: update zh_TW's documentation from an ascensive aspect
Date: Mon, 31 Jul 2023 10:09:16 -0600 [thread overview]
Message-ID: <877cqgdpw3.fsf@meer.lwn.net> (raw)
In-Reply-To: <87h6pm4ui5.fsf@meer.lwn.net>
Jonathan Corbet <corbet@lwn.net> writes:
> Hu Haowen <src.res.211@gmail.com> writes:
>
>> Did you receive my patches? Please get down to them soon because I have
>> another series of patches pending on until the current patches are
>> resolved.
>
> Yes, I receive your patches.
>
> I'll ask you again: please be a little more patient. I will get to
> them.
I still cannot apply your patches:
> WARNING: Message contains suspicious unicode control characters!
> Subject: [PATCH v2 5/6] docs/zh_TW: update process
> Line: .. _tw_process_statement_kernel:
> -------^
> Char: ZERO WIDTH NO-BREAK SPACE (0xfeff)
> If you are sure about this, rerun with the right flag to allow.
> AM FAILED
>
I'll ask again: please send me a version lacking weird Unicode control
characters.
Thanks,
jon
prev parent reply other threads:[~2023-07-31 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 4:17 [PATCH v2 0/6] docs/zh_TW: update zh_TW's documentation from an ascensive aspect Hu Haowen
2023-07-24 6:39 ` [PATCH v2 2/6] docs/zh_TW: update arch Hu Haowen
2023-07-24 6:39 ` [PATCH v2 3/6] docs/zh_TW: update cpu-freq Hu Haowen
2023-07-24 6:39 ` [PATCH v2 4/6] docs/zh_TW: update filesystems Hu Haowen
2023-07-24 6:39 ` [PATCH v2 6/6] docs/zh_TW: turn zh_CN's folder references and headers into zh_TW's ones Hu Haowen
2023-07-29 10:29 ` [PATCH v2 0/6] docs/zh_TW: update zh_TW's documentation from an ascensive aspect Hu Haowen
2023-07-29 15:17 ` Jonathan Corbet
2023-07-31 16:09 ` Jonathan Corbet [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=877cqgdpw3.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=src.res.211@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).