From: Yanteng Si <siyanteng@loongson.cn>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
ojeda@kernel.org, alex.gaynor@gmail.com, wedsonaf@gmail.com,
boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com,
benno.lossin@proton.me, a.hindborg@samsung.com,
aliceryhl@google.com, nathan@kernel.org, ndesaulniers@google.com,
morbo@google.com, justinstitt@google.com, alexs@kernel.org,
dzm91@hust.edu.cn, linux-doc@vger.kernel.org,
rust-for-linux@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v2 0/4] rust: docs: Update the translation of rust to 6.9-rc4
Date: Sat, 27 Apr 2024 19:00:21 +0800 [thread overview]
Message-ID: <96b9372f-b77b-4810-8fdf-5e5b02522bfc@loongson.cn> (raw)
In-Reply-To: <CANiq72kDEm7prV6ynAf=rZ5VydT=cYD-Ncj=waZEUOeCA1wbGA@mail.gmail.com>
在 2024/4/27 15:06, Miguel Ojeda 写道:
> On Sat, Apr 27, 2024 at 6:38 AM Yanteng Si <siyanteng@loongson.cn> wrote:
>> What I mean is that if I translate these two patches as two separate
>> patches,
> Ah, I see. As far as I know and from a quick look at the history, the
> translations try to be in sync with the latest non-translated status
> at their own pace, and they don't mimic the development of the
> non-translated side commit-by-commit.
>
> So I don't think particular commits should be translated as separate
> patches. In other words, what you did here in this v2 seems fine,
> since it already contains the "final state".
>
> Of course, there is a small risk of going out of sync with the current
> patch series if e.g. the RISC-V PR does not get eventually merged in
> the next merge window. This is why I mentioned that I am not sure what
> the policy is for translations here (e.g. there may be a requirement
> that patches to be applied to translations have been already applied
> to mainline, in which case you may want to send the RISC-V bit later
> -- but I don't know what the actual policy is).
>
Yes, our current update policy is a bit vague. Most of the time, this is
consistent with the latest state of the linux-next tree, but in the future
it may tend to be consistent with the latest state of the doc tree, Would
avoid the situation you're talking about with riscv.
The optimal solution is always to provide both Chinese and English
modifications. :)
Thanks,
Yanteng
next prev parent reply other threads:[~2024-04-27 11:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 6:59 [PATCH v2 0/4] rust: docs: Update the translation of rust to 6.9-rc4 Yanteng Si
2024-04-26 6:59 ` [PATCH v2 1/4] docs/zh_CN/rust: Update the translation of arch-support " Yanteng Si
2024-04-27 5:29 ` Dongliang Mu
2024-04-26 6:59 ` [PATCH v2 2/4] docs/zh_CN/rust: Update the translation of coding-guidelines " Yanteng Si
2024-04-27 5:29 ` Dongliang Mu
2024-04-26 7:02 ` [PATCH v2 3/4] docs/zh_CN/rust: Update the translation of general-information " Yanteng Si
2024-04-27 5:30 ` Dongliang Mu
2024-04-26 7:02 ` [PATCH v2 4/4] docs/zh_CN/rust: Update the translation of quick-start " Yanteng Si
2024-04-27 5:30 ` Dongliang Mu
2024-04-26 7:37 ` [PATCH v2 0/4] rust: docs: Update the translation of rust " Miguel Ojeda
2024-04-26 10:35 ` Yanteng Si
2024-04-26 10:35 ` Yanteng Si
2024-04-26 12:20 ` Miguel Ojeda
2024-04-26 12:20 ` Miguel Ojeda
2024-04-26 13:42 ` Jonathan Corbet
2024-04-26 16:47 ` Miguel Ojeda
2024-04-27 4:38 ` Yanteng Si
2024-04-27 7:06 ` Miguel Ojeda
2024-04-27 11:00 ` Yanteng Si [this message]
2024-04-27 4:25 ` Yanteng Si
2024-04-27 4:53 ` Dongliang Mu
2024-04-27 4:57 ` Dongliang Mu
2024-05-02 16:28 ` Jonathan Corbet
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=96b9372f-b77b-4810-8fdf-5e5b02522bfc@loongson.cn \
--to=siyanteng@loongson.cn \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=alexs@kernel.org \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=gary@garyguo.net \
--cc=justinstitt@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
/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.