mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hu Haowen <src.res.211@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc-tw-discuss@lists.sourceforge.net,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 0/6] docs/zh_TW: update zh_TW's documentation from an ascensive aspect
Date: Thu, 20 Jul 2023 23:30:50 +0800	[thread overview]
Message-ID: <671503c8-c5c9-f475-1085-2a5c551d74ea@gmail.com> (raw)
In-Reply-To: <877cqur8l6.fsf@meer.lwn.net>



On 2023/7/20 21:55, 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.
> 
> Is there a reason why you're resending a patch series from four days
> ago?

Considering for a long time but no reply, I just thought my patches were
ignored among the flood of emails or regarded as spam information.

Accordingly I resent my patches to ensure the reception of my patches as
well as added the cover email to provide an outline of my patch series.

Thanks,
Hu Haowen

> 
> Thanks,
> 
> jon

  reply	other threads:[~2023-07-20 15:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 13:27 Hu Haowen
2023-07-20 13:27 ` [PATCH RESEND 1/6] docs/zh_TW: update admin-guide Hu Haowen
2023-07-20 13:27 ` [PATCH RESEND 2/6] docs/zh_TW: update arch Hu Haowen
2023-07-20 13:27 ` [PATCH RESEND 3/6] docs/zh_TW: update cpu-freq Hu Haowen
2023-07-20 13:27 ` [PATCH RESEND 4/6] docs/zh_TW: update filesystems Hu Haowen
2023-07-20 13:27 ` [PATCH RESEND 5/6] docs/zh_TW: update process Hu Haowen
2023-07-20 13:27 ` [PATCH RESEND 6/6] docs/zh_TW: turn zh_CN's folder references and headers into zh_TW's ones Hu Haowen
2023-07-20 13:55 ` [PATCH RESEND 0/6] docs/zh_TW: update zh_TW's documentation from an ascensive aspect Jonathan Corbet
2023-07-20 15:30   ` Hu Haowen [this message]
2023-07-20 15:51     ` Jonathan Corbet
2023-07-21 19:44 ` Jonathan Corbet
2023-07-24 10:32   ` Hu Haowen

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=671503c8-c5c9-f475-1085-2a5c551d74ea@gmail.com \
    --to=src.res.211@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc-tw-discuss@lists.sourceforge.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®