From: Weijie Yuan <wy@wyuan.org>
To: linux-doc@vger.kernel.org
Cc: Alex Shi <alexs@kernel.org>, Dongliang Mu <dzm91@hust.edu.cn>,
Yanteng Si <si.yanteng@linux.dev>,
Chen-Yu Yeh <chenyou910331@gmail.com>
Subject: Re: What's cooking in Chinese docs (Aug 2026, #01)
Date: Wed, 19 Aug 2026 20:49:07 +0800 [thread overview]
Message-ID: <aoWmQ965W4WxU4yZ@wyuan.org> (raw)
In-Reply-To: <aoLkMBQszbzqYowy@wyuan.org>
On Mon, Aug 17, 2026 at 06:36:32PM +0800, Weijie Yuan wrote:
> Here are the topics waiting to be merged.
>
> Sorry for the late update.
>
> Last time, a contributor mentioned that he did not want to be copied, so
> this time I will only send it to the maintainer. Meanwhile, I am looking
> forward to the emergence of an automated system for our work. ;-)
>
>
> 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://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)
BTW, I just set up a mirror at github.com:
https://github.com/kernel-zh/linux-zh_CN
It uses a relatively bare-bones GitHub Action to sync from kernel.org
every day (I guess it can do every 2 hours as well, but every day seems
fine, as I'm afraid that if the frequency is too high, there might be
problems.)
I don't know much about GitHub Actions, so if you have a better solution
or thoughts on this, please let me know. Or, I would be very pleased to
invite you to take over the org account and set it up.
Although I know that people here may not be so fond of GitHub, this is
what I can do now.
Thanks.
prev parent reply other threads:[~2026-08-19 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 10:36 What's cooking in Chinese docs (Aug 2026, #01) Weijie Yuan
2026-08-19 12:49 ` 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=aoWmQ965W4WxU4yZ@wyuan.org \
--to=wy@wyuan.org \
--cc=alexs@kernel.org \
--cc=chenyou910331@gmail.com \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=si.yanteng@linux.dev \
/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