From: Jonathan Corbet <corbet@lwn.net>
To: Jiandong Qiu <qiujiandong1998@gmail.com>,
alexs@kernel.org, si.yanteng@linux.dev
Cc: dzm91@hust.edu.cn, skhan@linuxfoundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiandong Qiu <qiujiandong1998@gmail.com>
Subject: Re: [PATCH 0/3] docs/zh_CN: update translation of doc-guide/sphinx.rst
Date: Fri, 19 Jun 2026 08:26:26 -0600 [thread overview]
Message-ID: <87ldcatxm5.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260619140245.1982921-1-qiujiandong1998@gmail.com>
Jiandong Qiu <qiujiandong1998@gmail.com> writes:
> Hi all,
>
> This is my first time sending patches to the Linux community. I have
> been reading the kernel documentation to learn more about Linux, and in
> the process I found a few places where I could help improve the zh_CN
> translations. Comments and suggestions are welcome.
Thank you for working to improve our documentation!
I've added a couple of comments, though I need to defer to others to
judge the translation work itself. I do have one question, though: did
you do the translation yourself, or did you use some sort of tool? In
the latter case, you need to document that usage with Assisted-by tags.
Thanks,
jon
next prev parent reply other threads:[~2026-06-19 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 14:02 [PATCH 0/3] docs/zh_CN: update translation of doc-guide/sphinx.rst Jiandong Qiu
2026-06-19 14:02 ` [PATCH 1/3] docs/zh_CN: add llvm.rst translation anchor Jiandong Qiu
2026-06-19 14:23 ` Jonathan Corbet
2026-06-19 14:02 ` [PATCH 2/3] docs/zh_CN: add process/changes.rst translation Jiandong Qiu
2026-06-19 14:23 ` Jonathan Corbet
2026-06-19 16:25 ` Jiandong Qiu
2026-06-19 14:02 ` [PATCH 3/3] docs/zh_CN: update sphinx.rst translation Jiandong Qiu
2026-06-19 14:26 ` Jonathan Corbet [this message]
2026-06-19 16:28 ` [PATCH 0/3] docs/zh_CN: update translation of doc-guide/sphinx.rst Jiandong Qiu
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=87ldcatxm5.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=alexs@kernel.org \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiujiandong1998@gmail.com \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.