From: Alex Shi <seakeel@gmail.com>
To: dzm91@hust.edu.cn
Cc: alexs@kernel.org, corbet@lwn.net, frederic@kernel.org,
gpiccoli@igalia.com, jani.nikula@intel.com, kees@kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
longman@redhat.com, mchehab+huawei@kernel.org,
si.yanteng@linux.dev, skhan@linuxfoundation.org,
tony.luck@intel.com, zhuyan2015@qq.com
Subject: Re: [PATCH v2] docs/zh_CN: update admin-guide/index.rst translation
Date: Mon, 8 Jun 2026 09:40:11 +0800 [thread overview]
Message-ID: <b7606f72-eb55-41a7-b685-00164050e159@gmail.com> (raw)
In-Reply-To: <4534170c-700d-43b5-ad32-6b91455b3f14@hust.edu.cn>
Applied, Thanks!
next prev parent reply other threads:[~2026-06-08 1:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 15:37 [PATCH v2] docs/zh_CN: update admin-guide/index.rst translation Yan Zhu
2026-06-01 1:45 ` Dongliang Mu
2026-06-08 1:40 ` Alex Shi [this message]
2026-06-12 16:11 ` Yan Zhu
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=b7606f72-eb55-41a7-b685-00164050e159@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=frederic@kernel.org \
--cc=gpiccoli@igalia.com \
--cc=jani.nikula@intel.com \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mchehab+huawei@kernel.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=tony.luck@intel.com \
--cc=zhuyan2015@qq.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