From: Weijie Yuan <wy@wyuan.org>
To: Jiandong Qiu <qiujiandong1998@gmail.com>
Cc: linux-doc@vger.kernel.org, Alex Shi <alexs@kernel.org>,
Yanteng Si <si.yanteng@linux.dev>,
Dongliang Mu <dzm91@hust.edu.cn>, Ben Guo <ben.guo@openatom.club>,
Gary Guo <gary@garyguo.net>, Yan Zhu <zhuyan2015@qq.com>,
Doehyun Baek <doehyunbaek@gmail.com>,
chengyaqiang <chengyaqiang@chengyaqiang.com>
Subject: Re: What's cooking in zh_CN (Jul 2026)
Date: Tue, 14 Jul 2026 12:47:50 +0800 [thread overview]
Message-ID: <alW_di9bNNK9-zqM@wyuan.org> (raw)
In-Reply-To: <CAAJ18eFxjotuhggQ=wkSuXfyz5yVHE0LiP26STdcJwfdwAfF5w@mail.gmail.com>
On Tue, Jul 14, 2026 at 10:30:24AM +0800, Jiandong Qiu wrote:
> Just a thought: zh_CN/how-to.rst currently focuses mainly on submitting
> patches. If we want to encourage newcomers to review too, maybe we could
> add some guidance there on how to review, what to check and how to give
> feedback? Curious what others think.
Yeah, Although the current situation indicates that the pressure of
review is not very high at present, gradually distributing the review
work to the community would definitely not be a bad thing. Finally, it
would be best to have Alex, Dongliang and Yanteng handle the last pass.
I see that most of the patches are currently reviewed by Dongliang. This
is definitely fine, but having more pairs of eyes would be even better,
just as Linus Torvalds said.
For how-to.rst, maybe we can add a section?
btw, Git has a doc especially for review:
https://git-scm.com/docs/ReviewingGuidelines
we can have a look, then let's see what we can do.
next prev parent reply other threads:[~2026-07-14 4:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 16:49 What's cooking in zh_CN (Jul 2026) Weijie Yuan
2026-07-14 2:03 ` Alex Shi
2026-07-14 2:30 ` Jiandong Qiu
2026-07-14 4:47 ` Weijie Yuan [this message]
2026-07-14 9:32 ` Dongliang Mu
2026-07-14 9:51 ` Weijie Yuan
2026-07-14 9:54 ` Dongliang Mu
2026-07-14 10:15 ` Alex Shi
2026-07-14 12:16 ` Weijie Yuan
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=alW_di9bNNK9-zqM@wyuan.org \
--to=wy@wyuan.org \
--cc=alexs@kernel.org \
--cc=ben.guo@openatom.club \
--cc=chengyaqiang@chengyaqiang.com \
--cc=doehyunbaek@gmail.com \
--cc=dzm91@hust.edu.cn \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=qiujiandong1998@gmail.com \
--cc=si.yanteng@linux.dev \
--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