Linux Documentation
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Doehyun Baek <doehyunbaek@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>,
	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 01:42:27 +0800	[thread overview]
Message-ID: <alZ1AzLX8LrB-JFK@wyuan.org> (raw)
In-Reply-To: <CAN-j9UoUHQ2i4H+9G-XK_mOfKKyE9K9-mwUgPc+4yOVfiizgmA@mail.gmail.com>

On Tue, Jul 14, 2026 at 07:05:28PM +0200, Doehyun Baek wrote:
> I "cooked" up a small website this evening that attempts to automate them:
> 
> https://doehyunbaek.github.io/cook-linux-zhcn/
> 
> 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
> 
> Issues, suggestions, and pull requests are welcome!

Hi Doehyun,

Wow, at first glance, it seemed quite good, as a prototype.

I feel like your UI is kind of similar to sashiko? I'm fine with it.

I guess this might be the thing that Dongliang had in mind. Let's
wait for the comments from those in the UTC+8 time zone after they
wake up ;-)

Btw, for example, my patch (Weijie Yuan · docs/zh_CN: add docs-next
checkout workaround) is actually directly discarded after we reached
a consensus during our communication (with Dongliang). But it's
obvious that we didn't say it explicitly. So your website can't
recognize it automaticly right now. Perhaps we can think about how
to deal with this situation later.

Thanks for your effort,
Weijie

-- 
seems that your email doesn't show up as expected on
lore.kernel.org til now, confused..

  parent reply	other threads:[~2026-07-14 17:42 UTC|newest]

Thread overview: 5+ 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 [this message]
2026-07-14 17:56       ` Doehyun Baek
2026-07-14 18:17         ` 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=alZ1AzLX8LrB-JFK@wyuan.org \
    --to=wy@wyuan.org \
    --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=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