From: "Gary Guo" <gary@garyguo.net>
To: "Dongliang Mu" <dzm91@hust.edu.cn>, "Gary Guo" <gary@garyguo.net>,
"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, 09 Apr 2026 11:03:49 +0100 [thread overview]
Message-ID: <DHOJEMI0WBYX.2Y6HFZ2PYD7HS@garyguo.net> (raw)
In-Reply-To: <d7e81015-f17e-4ab9-a9e5-d2ac6dd82e7b@hust.edu.cn>
On Thu Apr 9, 2026 at 6:37 AM BST, Dongliang Mu wrote:
>
> On 4/9/26 1:43 AM, Gary Guo wrote:
>> On Wed Apr 8, 2026 at 5:51 PM BST, Ben Guo wrote:
>>> On 4/8/26 7:33 PM, Gary Guo wrote:
>>>> Hi Ben,
>>>>
>>>> Thanks on updating the doc translation. There has been new changes to
>>>> quick-start.rst on rust-next, could you update the translation to base on that
>>>> please?
>>>>
>>>> Thanks,
>>>> Gary
>>> Hi Gary,
>>>
>>>
>>>
>>>
>>>
>>> Thanks for the review. This series is based on the Chinese documentation
>>> maintainer's tree (alexs/linux.git docs-next), which does not yet have
>>> the latest quick-start.rst changes from the Rust-for-Linux rust-next
>>> tree.
>>>
>>> Would it be better to wait until those changes land in our base tree
>>> and then resend with the updated translation? Or would you prefer a
>>> different approach?
>>>
>>> Thanks,
>>> Ben
>> I don't see the issue of sending translation of the latest quick-start.rst even
>> if it's not in your base yet. By the time the changes land upstream, the
>> original quick-start.rst would already be there.
>
> 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.
Acked-by: Gary Guo <gary@garyguo.net> # Rust
Thanks,
Gary
next prev parent reply other threads:[~2026-04-09 10:03 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 [this message]
2026-04-09 13:51 ` Alex Shi
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=DHOJEMI0WBYX.2Y6HFZ2PYD7HS@garyguo.net \
--to=gary@garyguo.net \
--cc=alexs@kernel.org \
--cc=ben.guo@openatom.club \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--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