From: Yanteng Si <siyanteng@loongson.cn>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
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: Sat, 27 Apr 2024 12:38:20 +0800 [thread overview]
Message-ID: <f49129dd-ed6f-4940-b851-0282fc320234@loongson.cn> (raw)
In-Reply-To: <CANiq72mHoh=qgOGPj29hpS7EhVcXi5Q_7GYsycKhYwj3QbsTag@mail.gmail.com>
在 2024/4/27 00:47, Miguel Ojeda 写道:
> On Fri, Apr 26, 2024 at 3:42 PM Jonathan Corbet <corbet@lwn.net> wrote:
>> 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?
> Yeah, that is what I am thinking as well, although Yanteng is
> mentioning conflicts somewhere, so I may be missing something too.
>
Sorry, I may have made a mistake, there are no conflicts in this patch set.
What I mean is that if I translate these two patches as two separate
patches,
merge them into the rust tree, and then merge the rest of the patch set into
the doc tree, it might cause a conflict in the linux-next tree, because
in order
of order, the two patches have to be applied after this patch set. I'm
not sure
I've understood the whole process correctly.
Now that the two patches have become part of the patch set, there will be no
conflict no matter which tree is eventually merged into.
Thanks,
Yanteng
next prev parent reply other threads:[~2024-04-27 4:38 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
2024-04-26 16:47 ` Miguel Ojeda
2024-04-27 4:38 ` Yanteng Si [this message]
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=f49129dd-ed6f-4940-b851-0282fc320234@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 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).