From: Jonathan Corbet <corbet@lwn.net>
To: "Wu X.C." <bobwxc@email.cn>, Yanteng Si <siyanteng@loongson.cn>
Cc: alexs@kernel.org, chenhuacai@kernel.org, jiaxun.yang@flygoat.com,
linux-doc@vger.kernel.org, realpuyuwang@gmail.com,
siyanteng01@gmail.com, huangjianghui@uniontech.com
Subject: Re: [PATCH 1/3] docs/zh_CN: add parisc index translation
Date: Thu, 29 Apr 2021 10:16:01 -0600 [thread overview]
Message-ID: <87v985cbi6.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210429151058.GA23087@bobwxc.top>
"Wu X.C." <bobwxc@email.cn> writes:
> On Thu, Apr 29, 2021 at 11:33:33AM +0800, Yanteng Si wrote:
>> This path translates Documentation/parisc/index.rst into Chinese.
>>
>> Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
>
> Reviewed-by: Wu XiangCheng <bobwxc@email.cn>
>
> PA-RISC docs are silent, lastest practical activity on 2013-07-09.
Indeed...PA-RISC in general is not a hotbed of activity these days. Is
there some need in particular that is driving this translation? The
work is there and I'll apply it, but I do wonder why...
Thanks,
jon
next prev parent reply other threads:[~2021-04-29 16:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 3:33 [PATCH 0/3] docs/zh_CN: add parisc Chinese documents Yanteng Si
2021-04-29 3:33 ` [PATCH 1/3] docs/zh_CN: add parisc index translation Yanteng Si
2021-04-29 15:10 ` Wu X.C.
2021-04-29 16:16 ` Jonathan Corbet [this message]
[not found] ` <CAEensMxWmRppXmxuYEsq-jS-psQ8N1Zim-d+CCOckig__RfN5w@mail.gmail.com>
2021-04-30 6:59 ` yanteng si
2021-04-29 3:33 ` [PATCH 2/3] docs/zh_CN: add parisc debugging.rst translation Yanteng Si
2021-04-29 15:13 ` Wu X.C.
2021-05-04 6:56 ` yanteng si
2021-05-04 8:25 ` Wu X.C.
2021-05-06 6:09 ` yanteng si
2021-04-29 3:33 ` [PATCH 3/3] docs/zh_CN: add parisc registers.rst translation Yanteng Si
2021-04-29 15:15 ` Wu X.C.
2021-05-04 7:26 ` yanteng si
2021-05-06 9:48 ` yanteng si
2021-05-07 2:15 ` Wu X.C.
2021-05-07 3:00 ` yanteng si
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=87v985cbi6.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=chenhuacai@kernel.org \
--cc=huangjianghui@uniontech.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-doc@vger.kernel.org \
--cc=realpuyuwang@gmail.com \
--cc=siyanteng01@gmail.com \
--cc=siyanteng@loongson.cn \
/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).