* Re: What's cooking in zh_CN (Jul 2026, #02)
[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-15 1:46 ` Dongliang Mu
2026-07-15 1:43 ` Dongliang Mu
2026-07-15 1:52 ` Alex Shi
2 siblings, 2 replies; 9+ messages in thread
From: Weijie Yuan @ 2026-07-14 17:42 UTC (permalink / raw)
To: Doehyun Baek
Cc: linux-doc, Alex Shi, Yanteng Si, Dongliang Mu, Ben Guo, Gary Guo,
Yan Zhu, Jiandong Qiu, chengyaqiang, Haoyang Liu
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..
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: What's cooking in zh_CN (Jul 2026, #02)
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
1 sibling, 2 replies; 9+ messages in thread
From: Doehyun Baek @ 2026-07-14 17:56 UTC (permalink / raw)
To: Weijie Yuan
Cc: linux-doc, Alex Shi, Yanteng Si, Dongliang Mu, Ben Guo, Gary Guo,
Yan Zhu, Jiandong Qiu, chengyaqiang, Haoyang Liu
> 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.
Yeah, this is a downside of an automated approach: it can miss details
that are only implicit in the discussion. I see roughly three ways to
handle such cases:
1. Allow authors to mark a patch explicitly by replying with a
recognized phrase, such as `Patch-status: withdrawn`.
2. Use natural-language reasoning, perhaps with an LLM, to infer the
outcome from the discussion. I leaned against it due to cost and
complexity.
3. Leave the patch pending and let it move to “Cold” automatically
after 30 days.
I think either the first or the third option makes sense in this situation.
Thanks,
Doehyun
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: What's cooking in zh_CN (Jul 2026, #02)
2026-07-14 17:56 ` Doehyun Baek
@ 2026-07-14 18:17 ` Weijie Yuan
2026-07-15 1:55 ` Dongliang Mu
1 sibling, 0 replies; 9+ messages in thread
From: Weijie Yuan @ 2026-07-14 18:17 UTC (permalink / raw)
To: Doehyun Baek
Cc: linux-doc, Alex Shi, Yanteng Si, Dongliang Mu, Ben Guo, Gary Guo,
Yan Zhu, Jiandong Qiu, chengyaqiang, Haoyang Liu
On Tue, Jul 14, 2026 at 07:56:28PM +0200, Doehyun Baek wrote:
> > 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.
>
> Yeah, this is a downside of an automated approach: it can miss details
> that are only implicit in the discussion. I see roughly three ways to
> handle such cases:
>
> 1. Allow authors to mark a patch explicitly by replying with a
> recognized phrase, such as `Patch-status: withdrawn`.
> 2. Use natural-language reasoning, perhaps with an LLM, to infer the
> outcome from the discussion. I leaned against it due to cost and
> complexity.
> 3. Leave the patch pending and let it move to "Cold" automatically
> after 30 days.
Junio originally uses "Stalled", but I don't think there's a difference
though :-)
> I think either the first or the third option makes sense in this situation.
Agreed.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: What's cooking in zh_CN (Jul 2026, #02)
2026-07-14 17:56 ` Doehyun Baek
2026-07-14 18:17 ` Weijie Yuan
@ 2026-07-15 1:55 ` Dongliang Mu
1 sibling, 0 replies; 9+ messages in thread
From: Dongliang Mu @ 2026-07-15 1:55 UTC (permalink / raw)
To: Doehyun Baek, Weijie Yuan
Cc: linux-doc, Alex Shi, Yanteng Si, Ben Guo, Gary Guo, Yan Zhu,
Jiandong Qiu, chengyaqiang, Haoyang Liu
On 7/15/26 1:56 AM, Doehyun Baek wrote:
>> 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.
>
> Yeah, this is a downside of an automated approach: it can miss details
> that are only implicit in the discussion. I see roughly three ways to
> handle such cases:
>
> 1. Allow authors to mark a patch explicitly by replying with a
> recognized phrase, such as `Patch-status: withdrawn`.
This is better.
Or similar to syzbot, we can provide an option in the webpage to
directly mark patchset as invalid.
> 2. Use natural-language reasoning, perhaps with an LLM, to infer the
> outcome from the discussion. I leaned against it due to cost and
> complexity.
> 3. Leave the patch pending and let it move to “Cold” automatically
> after 30 days.
Better together with 1. We may forget to reply a mark patch when busy.
>
> I think either the first or the third option makes sense in this situation.
>
> Thanks,
> Doehyun
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: What's cooking in zh_CN (Jul 2026, #02)
2026-07-14 17:42 ` Weijie Yuan
2026-07-14 17:56 ` Doehyun Baek
@ 2026-07-15 1:46 ` Dongliang Mu
1 sibling, 0 replies; 9+ messages in thread
From: Dongliang Mu @ 2026-07-15 1:46 UTC (permalink / raw)
To: Weijie Yuan, Doehyun Baek
Cc: linux-doc, Alex Shi, Yanteng Si, Ben Guo, Gary Guo, Yan Zhu,
Jiandong Qiu, chengyaqiang, Haoyang Liu
On 7/15/26 1:42 AM, Weijie Yuan wrote:
> 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 ;-)
Yes, really awesome.
>
> 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.
We can set a terminal instruction like "Applied, thanks" to automate the
end of patches.
Dongliang Mu
>
> Thanks for your effort,
> Weijie
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: What's cooking in zh_CN (Jul 2026, #02)
[not found] ` <CAN-j9UoUHQ2i4H+9G-XK_mOfKKyE9K9-mwUgPc+4yOVfiizgmA@mail.gmail.com>
2026-07-14 17:42 ` Weijie Yuan
@ 2026-07-15 1:43 ` Dongliang Mu
2026-07-15 1:52 ` Alex Shi
2 siblings, 0 replies; 9+ messages in thread
From: Dongliang Mu @ 2026-07-15 1:43 UTC (permalink / raw)
To: Doehyun Baek, Weijie Yuan
Cc: linux-doc, Alex Shi, Yanteng Si, Ben Guo, Gary Guo, Yan Zhu,
Jiandong Qiu, chengyaqiang, Haoyang Liu
On 7/15/26 1:05 AM, 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/>
This is what I want. From this webpage, I can quickly locate patches
which needs review and start working.
>
> 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>
Let me take a look and think what I can help contribute.
>
> Issues, suggestions, and pull requests are welcome!
>
> Thanks,
> Doehyun
>
> On Tue, Jul 14, 2026 at 5:04 PM Weijie Yuan <wy@wyuan.org> wrote:
>
> On Tue, Jul 14, 2026 at 10:42:34PM +0800, Weijie Yuan wrote:
> > Here are the topics that have been cooking in Alex's tree.
>
> This statement is incorrect. I will correct it next time.
>
> Sorry for the noise.
>
> > Copies of the source code to Chinese documentation development
> tree live
> > in here:
> >
> >
> git://git.kernel.org/pub/scm/linux/kernel/git/alexs/linux.git
> <https://mail.hust.edu.cn:8443/linkserver?dest=http%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Falexs%2Flinux.git&tid=_____wAnVXVDblZqsIeJAA--.51119S3&rcpt=dzm91@hust.edu.cn&ifnotice=1&rindex=0>
> > https://git.kernel.org/pub/scm/linux/kernel/git/alexs/linux.git
> >
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/alexs/linux.git
> >
> > Mirrors:
> >
> > https://mirrors.hust.edu.cn/git/kernel-doc-zh.git
> > https://mirror.nju.edu.cn/git/kernel-doc-zh.git (experimental)
>
>
>
> --
> Doehyun Baek
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: What's cooking in zh_CN (Jul 2026, #02)
[not found] ` <CAN-j9UoUHQ2i4H+9G-XK_mOfKKyE9K9-mwUgPc+4yOVfiizgmA@mail.gmail.com>
2026-07-14 17:42 ` Weijie Yuan
2026-07-15 1:43 ` Dongliang Mu
@ 2026-07-15 1:52 ` Alex Shi
2 siblings, 0 replies; 9+ messages in thread
From: Alex Shi @ 2026-07-15 1:52 UTC (permalink / raw)
To: Doehyun Baek, Weijie Yuan
Cc: linux-doc, Alex Shi, Yanteng Si, Dongliang Mu, Ben Guo, Gary Guo,
Yan Zhu, Jiandong Qiu, chengyaqiang, Haoyang Liu
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
^ permalink raw reply [flat|nested] 9+ messages in thread