From: Alex Shi <seakeel@gmail.com>
To: Doehyun Baek <doehyunbaek@gmail.com>, Weijie Yuan <wy@wyuan.org>
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>,
Jiandong Qiu <qiujiandong1998@gmail.com>,
chengyaqiang <chengyaqiang@tsinghua.edu.cn>,
Haoyang Liu <tttturtleruss@gmail.com>
Subject: Re: What's cooking in zh_CN (Jul 2026, #02)
Date: Wed, 15 Jul 2026 09:52:20 +0800 [thread overview]
Message-ID: <143bc26b-5496-4770-a0a2-5ea1d1fed9da@gmail.com> (raw)
In-Reply-To: <CAN-j9UoUHQ2i4H+9G-XK_mOfKKyE9K9-mwUgPc+4yOVfiizgmA@mail.gmail.com>
On 2026/7/15 01:05, Doehyun Baek wrote:
> Hi Weijie,
>
> Thanks for putting together the “What’s cooking” reports!
> I "cooked" up a small website this evening that attempts to automate them:
>
> https://doehyunbaek.github.io/cook-linux-zhcn/
> <https://doehyunbaek.github.io/cook-linux-zhcn/>
Nice work!
Maybe add a build testing result for each of patches, like 'make
htmldocs -s', although build should pass before send out patches, but it
often be omitted.
> Every hour, a GitHub Actions workflow scans recent `docs/zh_CN` patches
> on the linux-doc mailing list, groups rerolls, and compares their
> subjects with Alex’s `docs-next` tree to determine whether they have
> been applied. Pending series with no update for more than 30 days are
> classified as “Cold.”
>
> This is still an experimental prototype, and its heuristics may have
> bugs, particularly when threads or patch subjects change. The source is
> available here:
>
> https://github.com/doehyunbaek/cook-linux-zhcn
> <https://github.com/doehyunbaek/cook-linux-zhcn>
> Issues, suggestions, and pull requests are welcome!
>
> Thanks,
> Doehyun
prev parent reply other threads:[~2026-07-15 1:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 14:42 What's cooking in zh_CN (Jul 2026, #02) Weijie Yuan
2026-07-14 15:04 ` Weijie Yuan
[not found] ` <CAN-j9UoUHQ2i4H+9G-XK_mOfKKyE9K9-mwUgPc+4yOVfiizgmA@mail.gmail.com>
2026-07-14 17:42 ` Weijie Yuan
2026-07-14 17:56 ` Doehyun Baek
2026-07-14 18:17 ` Weijie Yuan
2026-07-15 1:55 ` Dongliang Mu
2026-07-15 1:46 ` Dongliang Mu
2026-07-15 1:43 ` Dongliang Mu
2026-07-15 1:52 ` Alex Shi [this message]
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=143bc26b-5496-4770-a0a2-5ea1d1fed9da@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=ben.guo@openatom.club \
--cc=chengyaqiang@tsinghua.edu.cn \
--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=tttturtleruss@gmail.com \
--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