From: Hu Haowen <src.res@email.cn>
To: Jonathan Corbet <corbet@lwn.net>
Cc: panyunwang849@gmail.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] docs: add traditional Chinese translation for kernel Documentation
Date: Sun, 25 Jul 2021 22:30:31 +0800 [thread overview]
Message-ID: <b46316da-9c91-4407-649f-c3304e73696f@email.cn> (raw)
In-Reply-To: <87eebmwk9n.fsf@meer.lwn.net>
在 2021/7/25 下午10:17, Jonathan Corbet 写道:
> Hu Haowen <src.res@email.cn> writes:
>
>> Add traditional Chinese translation (zh_TW) for the Linux Kernel
>> documentation with a series of translated files.
>>
>> Signed-off-by: Hu Haowen <src.res@email.cn>
>> Reviewed-by: Pan Yunwang <panyunwang849@gmail.com>
> When you send a new version of a patch set, please include (after the
> "---" line) what changed. Otherwise maintainers have no idea why you
> keep sending the patch out or whether it seems to be stabilizing.
Sorry, forgot to append them.
v2:
* Added more translations for zh_TW.
v3:
* Fixed building errors.
* Added SPDX identifiers for each file.
v4:
* Reorganised patch format and compressed patch content.
v5:
* Added Reviewed-by tag.
Thx,
Hu Haowen
> Thanks,
>
> jon
next prev parent reply other threads:[~2021-07-25 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 14:25 [PATCH v4 1/2] docs: add traditional Chinese translation for kernel Documentation Hu Haowen
2021-07-21 14:25 ` [PATCH v4 2/2] docs/zh_TW: add translations for zh_TW/process Hu Haowen
2021-07-22 10:10 ` [PATCH v4 1/2] docs: add traditional Chinese translation for kernel Documentation Hu Haowen
2021-07-22 13:01 ` Pan Yunwang
2021-07-25 14:13 ` Hu Haowen
2021-07-25 14:14 ` [PATCH v5 " Hu Haowen
2021-07-25 14:14 ` [PATCH v5 2/2] docs/zh_TW: add translations for zh_TW/process Hu Haowen
2021-07-25 14:17 ` [PATCH v5 1/2] docs: add traditional Chinese translation for kernel Documentation Jonathan Corbet
2021-07-25 14:30 ` Hu Haowen [this message]
2021-07-25 20:27 ` Jonathan Corbet
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=b46316da-9c91-4407-649f-c3304e73696f@email.cn \
--to=src.res@email.cn \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=panyunwang849@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).