From: Weijie Yuan <wy@wyuan.org>
To: Alex Shi <seakeel@gmail.com>
Cc: Dongliang Mu <dzm91@hust.edu.cn>,
Dongliang Mu <mudongliangabcd@gmail.com>,
linux-doc@vger.kernel.org, Alex Shi <alexs@kernel.org>,
Yanteng Si <si.yanteng@linux.dev>,
Ben Guo <ben.guo@openatom.club>, Gary Guo <gary@garyguo.net>,
Yan Zhu <zhuyan2015@qq.com>, Doehyun Baek <doehyunbaek@gmail.com>,
Jiandong Qiu <qiujiandong1998@gmail.com>
Subject: Re: What's cooking in zh_CN (Jul 2026)
Date: Tue, 14 Jul 2026 20:16:25 +0800 [thread overview]
Message-ID: <alYomSIiGeUtQI1I@wyuan.org> (raw)
In-Reply-To: <b664685e-6785-44ae-8005-443032508096@gmail.com>
I took a look about patchwork, it is basically like a mailing-list
version issue tracker / pull-request dashboard.
It can manage patch backlog, assign patches, record CI results, and mark
patches as accepted, rejected, superseded, or under review. and record
trailers. Well, pretty much like a mini version of Gerrit or SourceHut.
But I think it's a little complicated for our needs, as it offers many
features that we might not actually need, which involves learning costs
and maintenance costs.
Just now, while going through patchwork of other lists a bit, I didn't
seem to find a way to filter out Chinese patches from the linux-doc
list, if we were to use it.
Dongliang, is the dashboard you want exactly like the one I sent in this
email, which is read-only? Or perhaps wish there are other functions as
well. For example, you can mark the patch series you have reviewed.
I can't find what IMA is btw.
[1] An exmaple of marking status of a patch in SourceHut
https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches/70509
next prev parent reply other threads:[~2026-07-14 12:16 UTC|newest]
Thread overview: 11+ 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
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 [this message]
2026-07-14 13:14 ` Dongliang Mu
2026-07-14 14:03 ` 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=alYomSIiGeUtQI1I@wyuan.org \
--to=wy@wyuan.org \
--cc=alexs@kernel.org \
--cc=ben.guo@openatom.club \
--cc=doehyunbaek@gmail.com \
--cc=dzm91@hust.edu.cn \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=mudongliangabcd@gmail.com \
--cc=qiujiandong1998@gmail.com \
--cc=seakeel@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