rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Yanteng Si <siyanteng@loongson.cn>
Cc: 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: Fri, 26 Apr 2024 07:42:08 -0600	[thread overview]
Message-ID: <87zftgnsun.fsf@meer.lwn.net> (raw)
In-Reply-To: <CANiq72meE9txt5b09Y7cUJd-hEqcZX1ZtRc_0YYDZqWQgyo3wA@mail.gmail.com>

Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> writes:

> On Fri, Apr 26, 2024 at 9:00 AM Yanteng Si <siyanteng@loongson.cn> wrote:
>>
>> v2:
>> * As Miguel's comments, translate commit 01848eee20c6
>>   into Chinese, as well as commit 81889e8523e6. By the way,
>>   these two patches haven't appeared in the doc development
>>   tree yet, maybe we could consider merging them into the
>>   rust tree?
>
> The former is in `rust-fixes`, which will be sent to Linus for this
> cycle. So the English docs will be updated sooner than these updates,
> if that is what you are asking.
>
> For the other one, it is in the RISC-V tree and I assume it will be
> sent into the next merge window. I don't know how you normally handle
> that (i.e. translations being updated at the same time or after a
> cycle), but either way, I am not sure why you would want them to be
> merged into the Rust tree?

I guess I don't see any reason why the translation couldn't go through
docs-next as usual?  It will all even out during the merge window,
right?  Or am I missing something?

Thanks,

jon

  parent reply	other threads:[~2024-04-26 13:42 UTC|newest]

Thread overview: 21+ 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 12:20     ` Miguel Ojeda
2024-04-26 13:42   ` Jonathan Corbet [this message]
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
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=87zftgnsun.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --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=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=siyanteng@loongson.cn \
    --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 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).