From: Jonathan Corbet <corbet@lwn.net>
To: Hu Haowen <src.res.211@gmail.com>
Cc: Hu Haowen <src.res.211@gmail.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] docs/zh_TW: update contents for zh_TW
Date: Tue, 03 Oct 2023 10:35:34 -0600 [thread overview]
Message-ID: <87ttr7d5pl.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230925052311.20992-1-src.res.211@gmail.com>
Hu Haowen <src.res.211@gmail.com> writes:
> The content of zh_TW was too outdated comparing to the original files.
> Consequently carry out improvements in order to both keep track of sources
> and fix several grammatical mistakes in traditional Chinese.
>
> This is a thorough rewrite of the previous patch:
> https://lore.kernel.org/linux-doc/20230807120006.6361-1-src.res.211@gmail.com/
> in order to get rid of text damage and merging errors, created based on
> linux-next (date: Sept. 15, 2023).
>
> Signed-off-by: Hu Haowen <src.res.211@gmail.com>
This version does not apply either:
Applying: docs/zh_TW: update contents for zh_TW
.git/rebase-apply/patch:751: new blank line at EOF.
+
.git/rebase-apply/patch:1061: new blank line at EOF.
+
.git/rebase-apply/patch:1411: new blank line at EOF.
+
.git/rebase-apply/patch:1443: new blank line at EOF.
+
.git/rebase-apply/patch:1717: new blank line at EOF.
+
error: patch failed: Documentation/translations/zh_TW/process/kernel-enforcement-statement.rst:1
error: Documentation/translations/zh_TW/process/kernel-enforcement-statement.rst: patch does not apply
error: Did you hand edit your patch?
It also apparently didn't make it into lore, for reasons unknown. Try
(yet) again?
jon
prev parent reply other threads:[~2023-10-03 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 5:23 [PATCH v2] docs/zh_TW: update contents for zh_TW Hu Haowen
2023-10-03 16:35 ` 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=87ttr7d5pl.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