rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Yanteng Si <siyanteng@loongson.cn>
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 14:20:02 +0200	[thread overview]
Message-ID: <CANiq72=b=G3GPVWQ2XV1MT-wdT0KL4jZVQfD55Mcz_st-G7r=Q@mail.gmail.com> (raw)
In-Reply-To: <9cae4c4a-55a6-4c6c-9780-866f796a52c0@loongson.cn>

On Fri, Apr 26, 2024 at 12:35 PM Yanteng Si <siyanteng@loongson.cn> wrote:
>
> 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.

Hmm... I am not sure I follow -- conflicts with what? These patches
only change the translations and they all get applied by the doc tree,
right?

Cheers,
Miguel

  reply	other threads:[~2024-04-26 12:21 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 [this message]
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
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='CANiq72=b=G3GPVWQ2XV1MT-wdT0KL4jZVQfD55Mcz_st-G7r=Q@mail.gmail.com' \
    --to=miguel.ojeda.sandonis@gmail.com \
    --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=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).