From: Alex Shi <seakeel@gmail.com>
To: Dongliang Mu <dzm91@hust.edu.cn>, Weijie Yuan <wy@wyuan.org>,
Dongliang Mu <mudongliangabcd@gmail.com>
Cc: 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 18:15:49 +0800 [thread overview]
Message-ID: <b664685e-6785-44ae-8005-443032508096@gmail.com> (raw)
In-Reply-To: <cc922c1b-49a5-4c3a-855c-af8eb6539f62@hust.edu.cn>
On 2026/7/14 17:54, Dongliang Mu wrote:
>>>> Since I made many noise these days on the list, which took up a lot of
>>>> maintainers' time. This email summarizes the patches for zh_CN that are
>>>> currently pending on the mailing list.
>>> This is awesome. Maybe we can establish a dashboard for the activities
>>> in zh_CN/TW related patches of linux-doc.
>>>
>>> I personally kept a knowledge base in the IMA (an app for storing
>>> knowledge base in the cloud) in our club to monitor these activities.
>> I remember kernel.org itself already provides this:
>>
>> https://patchwork.kernel.org/
>>
>> Is this similar to your idea? But I haven't look deep into patchwork
>> before.
>>
>> Of source, having our own thing is definitely okay.
>
>
> I am not familar with patchwork too. How about Alex?
I don't know if the patchwork has a similar feature like this email,
does it?
Thanks!
next prev parent reply other threads:[~2026-07-14 10:15 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 [this message]
2026-07-14 12:16 ` Weijie Yuan
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=b664685e-6785-44ae-8005-443032508096@gmail.com \
--to=seakeel@gmail.com \
--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=si.yanteng@linux.dev \
--cc=wy@wyuan.org \
--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