From: Weijie Yuan <wy@wyuan.org>
To: Dongliang Mu <dzm91@hust.edu.cn>
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs/zh_CN: add docs-next checkout workaround
Date: Fri, 10 Jul 2026 21:36:47 +0800 [thread overview]
Message-ID: <alD1b7O6KaIMqWpa@wyuan.org> (raw)
In-Reply-To: <ce715802-1b46-4ba6-b388-39260f217ba3@hust.edu.cn>
On Fri, Jul 10, 2026 at 09:21:16PM +0800, Dongliang Mu wrote:
>
> On 7/9/26 11:25 PM, Weijie Yuan wrote:
> > Hi all,
> >
> > Since cloning Alex Shi's tree from the HUST mirror may be unstable, as
> > reported in [1]. I think adding one more option for beginners to get
> > started might be a good idea.
> >
> > Thanks,
> > Weijie
> >
> > [1] https://lore.kernel.org/linux-doc/4292BADB2022F3A5+5117009.JcJflTAXpt@anka-vmware20-1/
> >
> > --- >8 ---
> Is this a special mark for LKML? If I understand correctly, the following
> should be the patch content.
Yes, the following is the commit message body.
You can apply this patch by "git am -c" or "git am --scissors", which
means: Remove everything in body before a scissors line (see git-mailinfo[1]).
https://git-scm.com/docs/git-am#Documentation/git-am.txt---scissors
Git community sometimes use it, for the cases if you want to swap the
actual commit message and the supplementary information.
> >
> > The Chinese documentation guide asks contributors to base their work on
> > the docs-next branch of Alex Shi's tree. However, cloning that tree from
> > git.kernel.org or mirrors.hust.edu.cn may fail in some network
> > environments.
> >
> > Document an alternative workflow: clone Linus Torvalds' tree from a
> > local mirror, add Alex Shi's tree as another remote, fetch docs-next
> > from it, and then create a local branch that tracks alexs/docs-next.
> >
> > Signed-off-by: Weijie Yuan <wy@wyuan.org>
> > ---
> > Documentation/translations/zh_CN/how-to.rst | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git a/Documentation/translations/zh_CN/how-to.rst b/Documentation/translations/zh_CN/how-to.rst
> > index 9ec2384e1e76..fcfe0a4a8be2 100644
> > --- a/Documentation/translations/zh_CN/how-to.rst
> > +++ b/Documentation/translations/zh_CN/how-to.rst
> > @@ -53,6 +53,16 @@ Linux 发行版和简单地使用 Linux 命令行,那么可以迅速开始了
> > 这是 Alex 开发树的镜像库,每两个小时同步一次上游。如果您了解到更快的 mirror,
> > 请随时 **添加** 。
> > +或者::
> > +
> > + git clone https://mirrors.tuna.tsinghua.edu.cn/git/linux.git
> > + cd linux
> > + git remote add alexs https://git.kernel.org/pub/scm/linux/kernel/git/alexs/linux.git/
> > + git fetch alexs docs-next:refs/remotes/alexs/docs-next
> > + git switch -c docs-next --track alexs/docs-next
> > +
> > +这将先用清华源拉取 Linus Torvalds 的开发树,再增量下载中文开发分支中的内容。
>
> This would make the envionment preparation more difficult. My suggestion is
> to ask maintainers of some mirror sites to sync this repo like us.
>
> Dongliang Mu
Makes sense. Could I kindly ask, for example, Tsinghua tuna team to
mirror our repo, on behalf of our Chinese document team? I'm afraid they
are unlikely to consider my request in my individual capacity. ;-)
Thanks,
Weijie
next prev parent reply other threads:[~2026-07-10 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 15:25 [PATCH] docs/zh_CN: add docs-next checkout workaround Weijie Yuan
2026-07-10 13:21 ` Dongliang Mu
2026-07-10 13:36 ` Weijie Yuan [this message]
2026-07-10 13:44 ` Dongliang Mu
2026-07-10 13:57 ` Weijie Yuan
2026-07-10 14:04 ` Dongliang Mu
2026-07-12 4:47 ` Dongliang Mu
2026-07-12 5:45 ` Weijie Yuan
2026-07-12 6:53 ` Weijie Yuan
2026-07-12 8:35 ` Dongliang Mu
2026-07-12 13:42 ` 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=alD1b7O6KaIMqWpa@wyuan.org \
--to=wy@wyuan.org \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
/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