linux-kernel - Re: [PATCH v2] docs/zh_TW: update contents for zh

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87ttr7d5pl.fsf@meer.lwn.net>
Date:   Tue, 03 Oct 2023 10:35:34 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Hu Haowen <src.res.211@...il.com>
Cc:     Hu Haowen <src.res.211@...il.com>, linux-kernel@...r.kernel.org,
        linux-doc@...r.kernel.org
Subject: Re: [PATCH v2] docs/zh_TW: update contents for zh_TW

Hu Haowen <src.res.211@...il.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@...il.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