Linux Documentation
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Dongliang Mu <dzm91@hust.edu.cn>
Cc: Alex Shi <seakeel@gmail.com>,
	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 22:03:40 +0800	[thread overview]
Message-ID: <alZBvMsD9gP_rbrd@wyuan.org> (raw)
In-Reply-To: <53ffbf05-7b2e-4ffa-945d-2a415e843cff@hust.edu.cn>

On Tue, Jul 14, 2026 at 09:14:38PM +0800, Dongliang Mu wrote:
> > 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.
> 
> Actually I just need a list of patches which I need to review, which I
> reviewed before and be resubmitted, and which is applied.

OK, let me think about it for a night.

In the afternoon, I came up with a rather crude method, which is...

Simply directly upload the plain text of "What's cooking" to a website
with Git. But of course, it wasn't updated immediately. It required
manual update. Do you think automatic synchronization is important?
I guess it is expected that the implementation automatic synchronization
will not be too easy, if we want it perfect.

It's not too much trouble for me to update manually now, but I expect to
try using shell scripts to improve efficiency next.

> > I can't find what IMA is btw.
> 
> https://ima.qq.com/
> 
> It is closed-source software from Tencent. This software cannot solve our
> problem.
> 
> I just put all the related linux-doc patches into the knowledge base, and
> ask in NLP about the activities in the linux-doc mailing list

Got it. I'll take a look though.

      reply	other threads:[~2026-07-14 14:03 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
2026-07-14 13:14           ` Dongliang Mu
2026-07-14 14:03             ` Weijie Yuan [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=alZBvMsD9gP_rbrd@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