From: Yanteng Si <siyanteng@loongson.cn>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: ojeda@kernel.org, corbet@lwn.net, 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, linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 0/4] rust: docs: Update the translation of rust to 6.9-rc4
Date: Fri, 26 Apr 2024 18:35:43 +0800 [thread overview]
Message-ID: <9cae4c4a-55a6-4c6c-9780-866f796a52c0@loongson.cn> (raw)
In-Reply-To: <CANiq72meE9txt5b09Y7cUJd-hEqcZX1ZtRc_0YYDZqWQgyo3wA@mail.gmail.com>
在 2024/4/26 15:37, Miguel Ojeda 写道:
>> 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.
Well, it seems that we will have to wait for the doc tree, because the
Chinese
translation is now carried out under the doc tree.
>
> 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'm thinking that I'm two commits ahead of the doc tree, it doesn't seem
to fit
merge into the doc tree in this window, and there might be conflicts on
linux-next if I splite the patch out more.
Thanks,
Yanteng
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next parent reply other threads:[~2024-04-26 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1714113680.git.siyanteng@loongson.cn>
[not found] ` <CANiq72meE9txt5b09Y7cUJd-hEqcZX1ZtRc_0YYDZqWQgyo3wA@mail.gmail.com>
2024-04-26 10:35 ` Yanteng Si [this message]
2024-04-26 12:20 ` [PATCH v2 0/4] rust: docs: Update the translation of rust to 6.9-rc4 Miguel Ojeda
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=9cae4c4a-55a6-4c6c-9780-866f796a52c0@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=linux-riscv@lists.infradead.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).