From: Weijie Yuan <wy@wyuan.org>
To: Dongliang Mu <dzm91@hust.edu.cn>
Cc: linux-doc@vger.kernel.org, Alex Shi <alexs@kernel.org>,
Yanteng Si <si.yanteng@linux.dev>,
Chen-Yu Yeh <chenyou910331@gmail.com>
Subject: Re: What's cooking in Chinese docs (Aug 2026, #01)
Date: Fri, 21 Aug 2026 21:43:15 +0800 [thread overview]
Message-ID: <aohV85J4mBKAxDwV@wyuan.org> (raw)
In-Reply-To: <01451650-af87-4362-bda2-3ba17fda386a@hust.edu.cn>
On Fri, Aug 21, 2026 at 09:06:52PM +0800, Dongliang Mu wrote:
> > > 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
>
> That's a good idea. I remember Haowen maintained his tree in the Github.
Yes, and I planned to put a zh_TW tree on it later, but no decided yet.
I need a little time to think about it. By the way, I´ve also been
talking with folks from l10n-tw recently, hoping to get more people
involved. Some have mentioned that the email-based workflow is a bit
cumbersome and that the barrier to entry is somewhat high.
and they are doing this job differently:
https://github.com/localizethedocs/linux-docs-l10n
I will communicate with them later to see if we can cooperate or not.
> Maybe CDN is also worth a try.
>
> We will setup a code hosting platform in the HUST. It's not a good idea to
> host git repository in the mirror site.
I recently came across your work - it looks great, and I'm looking
forward to seeing where it goes! And yes, the load and cost of running
mirror sites have been getting higher and higher lately, sadly.
> > 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.
>
> LLM helps here. It does not need any sophisticated technique.
Yes. And it seems there's no problem with the synchronization these two
days.
Thanks!
next prev parent reply other threads:[~2026-08-21 13:43 UTC|newest]
Thread overview: 6+ 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
2026-08-21 13:06 ` Dongliang Mu
2026-08-21 13:43 ` Weijie Yuan [this message]
2026-08-21 14:11 ` Dongliang Mu
2026-08-21 14: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=aohV85J4mBKAxDwV@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.