From: Alex Shi <seakeel@gmail.com>
To: Gary Guo <gary@garyguo.net>, Dongliang Mu <dzm91@hust.edu.cn>,
Ben Guo <ben.guo@openatom.club>, Alex Shi <alexs@kernel.org>,
Yanteng Si <si.yanteng@linux.dev>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH 3/4] docs/zh_CN: update rust/quick-start.rst translation
Date: Thu, 9 Apr 2026 21:51:27 +0800 [thread overview]
Message-ID: <909032ed-a67e-42e2-8f34-b5bc5472b1a4@gmail.com> (raw)
In-Reply-To: <DHOJEMI0WBYX.2Y6HFZ2PYD7HS@garyguo.net>
On 2026/4/9 18:03, Gary Guo wrote:
>> Hi Gary,
>>
>> Let’s wait for the rust-next changes to land upstream first, then I’ll
>> ask Ben Guo to sync that commit. Otherwise, the Chinese translation
>> would do not match the original English doc, which will confuse readers.
>>
>> We have checktransupdate.py in place for monitoring the updates in
>> English documents.
>>
>> Dongliang Mu
> Given that you have tools to catch this, I'm also okay with this patch landing
> as is, with a follow up translation when the new quick-start.rst lands upstream.
>
It's better to have the full translation after the formal English
documents merging into upstream instead of several parts to combine for
a whole document.
Thanks
Alex
next prev parent reply other threads:[~2026-04-09 13:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 5:05 [PATCH 0/4] docs/zh_CN: update rust/ subsystem translations Ben Guo
2026-04-08 5:05 ` [PATCH 1/4] docs/zh_CN: update rust/arch-support.rst translation Ben Guo
2026-04-08 11:31 ` Gary Guo
2026-04-08 5:05 ` [PATCH 2/4] docs/zh_CN: update rust/coding-guidelines.rst translation Ben Guo
2026-04-08 11:32 ` Gary Guo
2026-04-08 5:05 ` [PATCH 3/4] docs/zh_CN: update rust/quick-start.rst translation Ben Guo
2026-04-08 11:33 ` Gary Guo
2026-04-08 16:51 ` Ben Guo
2026-04-08 17:43 ` Gary Guo
2026-04-09 5:37 ` Dongliang Mu
2026-04-09 10:03 ` Gary Guo
2026-04-09 13:51 ` Alex Shi [this message]
2026-04-08 5:05 ` [PATCH 4/4] docs/zh_CN: update rust/index.rst translation Ben Guo
2026-04-08 11:33 ` Gary Guo
2026-04-08 11:44 ` [PATCH 0/4] docs/zh_CN: update rust/ subsystem translations Dongliang Mu
2026-04-08 16:54 ` Ben Guo
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=909032ed-a67e-42e2-8f34-b5bc5472b1a4@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=ben.guo@openatom.club \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=si.yanteng@linux.dev \
/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