[PATCH] docs/zh_CN: add docs-next checkout workaround

[PATCH] docs/zh_CN: add docs-next checkout workaround

[Weijie Yuan]

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 ---

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 的开发树，再增量下载中文开发分支中的内容。
+
 命令执行完毕后，您会在当前目录下得到一个 linux 目录，该目录就是您之后的工作
 仓库，请把它放在一个稳妥的位置。
 
-- 
2.55.0.795.g602f6c329a

Re: [PATCH] docs/zh_CN: add docs-next checkout workaround

[Dongliang Mu]

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.
>
> 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

> +
>   命令执行完毕后，您会在当前目录下得到一个 linux 目录，该目录就是您之后的工作
>   仓库，请把它放在一个稳妥的位置。
>   

Re: [PATCH] docs/zh_CN: add docs-next checkout workaround

[Weijie Yuan]

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

Re: [PATCH] docs/zh_CN: add docs-next checkout workaround

[Dongliang Mu]

On 7/10/26 9:36 PM, Weijie Yuan wrote:
> 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.
Understood.
>
>>> 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. ;-)

I can help contact TUNA maintainers.

Dongliang Mu

>
> Thanks,
> Weijie

Re: [PATCH] docs/zh_CN: add docs-next checkout workaround

[Weijie Yuan]

On Fri, Jul 10, 2026 at 09:44:45PM +0800, Dongliang Mu wrote:
> > > > --- >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.
> Understood.

Sorry for any confusion.

> > > 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. ;-)
> 
> I can help contact TUNA maintainers.
> 
> Dongliang Mu

That would be great! Apparently your words carry more weight than mine
;-) So do you mean that I just need to wait quietly for your good news?

Appreciate it!

Thanks,
Weijie

Re: [PATCH] docs/zh_CN: add docs-next checkout workaround

[Dongliang Mu]

On 7/10/26 9:57 PM, Weijie Yuan wrote:
> On Fri, Jul 10, 2026 at 09:44:45PM +0800, Dongliang Mu wrote:
>>>>> --- >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.
>> Understood.
> Sorry for any confusion.
>
>>>> 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. ;-)
>> I can help contact TUNA maintainers.
>>
>> Dongliang Mu
> That would be great! Apparently your words carry more weight than mine
> ;-) So do you mean that I just need to wait quietly for your good news?

Yes, I have explained the situation to TUNA maintainers and asked for 
repository syncing. Let's wait for their response.

Dongliang Mu

>
> Appreciate it!
>
> Thanks,
> Weijie

Re: [PATCH] docs/zh_CN: add docs-next checkout workaround

[Dongliang Mu]

On 7/10/26 9:57 PM, Weijie Yuan wrote:
> On Fri, Jul 10, 2026 at 09:44:45PM +0800, Dongliang Mu wrote:
>>>>> --- >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.
>> Understood.
> Sorry for any confusion.
>
>>>> 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. ;-)
>> I can help contact TUNA maintainers.
>>
>> Dongliang Mu
> That would be great! Apparently your words carry more weight than mine
> ;-) So do you mean that I just need to wait quietly for your good news?
Hi Weijie,
Could you please try cloning 
https://mirror.nju.edu.cn/git/kernel-doc-zh.git/ 
<https://link.wtturl.cn/?target=https%3A%2F%2Fmirror.nju.edu.cn%2Fgit%2Fkernel-doc-zh.git%2F&scene=im&aid=582478&lang=zh> 
and verify whether this mirror is stable?
TUNA has limited storage capacity and has asked the NJU mirror site to 
host this Git repository.
We are currently diagnosing network issues on our mirror site. The 
classic architecture — Nginx (serving static frontend, HTTPS, and 
caching) → Apache (reverse proxy + CGI execution) → cgit / 
git-http-backend — appears to be functional in principle.
The clone failures with large Git repositories are likely caused by 
insufficient or inappropriate parameter configurations rather than the 
architecture itself.
P.S., I am the mentor of HUST OpenAtom Club, and our club is maintaining 
the hust mirror site.
Dongliang Mu
>
> Appreciate it!
>
> Thanks,
> Weijie

Re: [PATCH] docs/zh_CN: add docs-next checkout workaround

[Weijie Yuan]

On Sun, Jul 12, 2026 at 12:47:16PM +0800, Dongliang Mu wrote:
> Hi Weijie,
> Could you please try cloning
> https://mirror.nju.edu.cn/git/kernel-doc-zh.git/ <https://link.wtturl.cn/?target=https%3A%2F%2Fmirror.nju.edu.cn%2Fgit%2Fkernel-doc-zh.git%2F&scene=im&aid=582478&lang=zh>
> and verify whether this mirror is stable?

OK, I just did a quick test on my debian 13 (local physical server):

$ git clone https://mirror.nju.edu.cn/git/kernel-doc-zh.git/
Cloning into 'kernel-doc-zh'...
remote: Enumerating objects: 11675982, done.
remote: Counting objects: 100% (11675982/11675982), done.
remote: Compressing objects: 100% (2008049/2008049), done.
error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
error: 7397 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

then again:

GIT_TRACE=1 \
GIT_TRACE_CURL=1 \
GIT_CURL_VERBOSE=1 \
git clone https://mirror.nju.edu.cn/git/kernel-doc-zh.git/

[...many verbose outputs]
remote: Enumerating objects: 11675982, done.
remote: Counting objects: 100% (11675982/11675982), done.
remote: Compressing objects: 100% (2008049/2008049), done.
13:24:10.505880 http.c:994              == Info: HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
13:24:10.505973 http.c:994              == Info: Connection #0 to host mirror.nju.edu.cn left intact
error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
error: 6191 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

From the output, it seems that there was an error in the mirror of NJU's
nginx, the Git HTTP backend behind nginx, or the upstream connection
between them, but I'm not 100% sure.

I will conduct several more tests immediately to troubleshoot the
problem, to see where exactly the problem lies.

In addition, cloning with a cloud server in Hong Kong:

Cloning into 'kernel-doc-zh'...
remote: Enumerating objects: 11675982, done.
remote: Counting objects: 100% (11675982/11675982), done.
remote: Compressing objects: 100% (2008049/2008049), done.
error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
error: 3965 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

> TUNA has limited storage capacity and has asked the NJU mirror site to host
> this Git repository.

Fully understand, easy to notice that TUNA is under big preesure these days.
Thanks, NJU!

> We are currently diagnosing network issues on our mirror site. The classic
> architecture - Nginx (serving static frontend, HTTPS, and caching) -> Apache
> (reverse proxy + CGI execution) -> cgit / git-http-backend - appears to be
> functional in principle.
> The clone failures with large Git repositories are likely caused by
> insufficient or inappropriate parameter configurations rather than the
> architecture itself.

Agreed, it is very likely that the transmission problem is caused by the
large size of the warehouse.

> P.S., I am the mentor of HUST OpenAtom Club, and our club is maintaining the
> hust mirror site.

Thanks very much.

Re: [PATCH] docs/zh_CN: add docs-next checkout workaround

[Weijie Yuan]

On Sun, Jul 12, 2026 at 01:45:36PM +0800, Weijie Yuan wrote:
> > We are currently diagnosing network issues on our mirror site. The classic
> > architecture - Nginx (serving static frontend, HTTPS, and caching) -> Apache
> > (reverse proxy + CGI execution) -> cgit / git-http-backend - appears to be
> > functional in principle.
> > The clone failures with large Git repositories are likely caused by
> > insufficient or inappropriate parameter configurations rather than the
> > architecture itself.
> 
> Agreed, it is very likely that the transmission problem is caused by the
> large size of the warehouse.

Oops, I mean repo of course.

Re: [PATCH] docs/zh_CN: add docs-next checkout workaround

[Dongliang Mu]

On 7/12/26 1:45 PM, Weijie Yuan wrote:
> On Sun, Jul 12, 2026 at 12:47:16PM +0800, Dongliang Mu wrote:
>> Hi Weijie,
>> Could you please try cloning
>> https://mirror.nju.edu.cn/git/kernel-doc-zh.git/ <https://link.wtturl.cn/?target=https%3A%2F%2Fmirror.nju.edu.cn%2Fgit%2Fkernel-doc-zh.git%2F&scene=im&aid=582478&lang=zh>
>> and verify whether this mirror is stable?
> OK, I just did a quick test on my debian 13 (local physical server):
>
> $ git clone https://mirror.nju.edu.cn/git/kernel-doc-zh.git/
> Cloning into 'kernel-doc-zh'...
> remote: Enumerating objects: 11675982, done.
> remote: Counting objects: 100% (11675982/11675982), done.
> remote: Compressing objects: 100% (2008049/2008049), done.
> error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
> error: 7397 bytes of body are still expected
> fetch-pack: unexpected disconnect while reading sideband packet
> fatal: early EOF
> fatal: fetch-pack: invalid index-pack output
>
> then again:
>
> GIT_TRACE=1 \
> GIT_TRACE_CURL=1 \
> GIT_CURL_VERBOSE=1 \
> git clone https://mirror.nju.edu.cn/git/kernel-doc-zh.git/
>
> [...many verbose outputs]
> remote: Enumerating objects: 11675982, done.
> remote: Counting objects: 100% (11675982/11675982), done.
> remote: Compressing objects: 100% (2008049/2008049), done.
> 13:24:10.505880 http.c:994              == Info: HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
> 13:24:10.505973 http.c:994              == Info: Connection #0 to host mirror.nju.edu.cn left intact
> error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
> error: 6191 bytes of body are still expected
> fetch-pack: unexpected disconnect while reading sideband packet
> fatal: early EOF
> fatal: fetch-pack: invalid index-pack output


It seems like the same issue with our mirror site. I've forward this 
email thread to NJU mirror maintainers.


>  From the output, it seems that there was an error in the mirror of NJU's
> nginx, the Git HTTP backend behind nginx, or the upstream connection
> between them, but I'm not 100% sure.
>
> I will conduct several more tests immediately to troubleshoot the
> problem, to see where exactly the problem lies.
>
> In addition, cloning with a cloud server in Hong Kong:
>
> Cloning into 'kernel-doc-zh'...
> remote: Enumerating objects: 11675982, done.
> remote: Counting objects: 100% (11675982/11675982), done.
> remote: Compressing objects: 100% (2008049/2008049), done.
> error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
> error: 3965 bytes of body are still expected
> fetch-pack: unexpected disconnect while reading sideband packet
> fatal: early EOF
> fatal: fetch-pack: invalid index-pack output


I tried the NJU mirror in my laptop, and successfully clone the 
repository from NJU mirror. There must exist some unknown reason to lead 
to this failure.


>
>> TUNA has limited storage capacity and has asked the NJU mirror site to host
>> this Git repository.
> Fully understand, easy to notice that TUNA is under big preesure these days.
> Thanks, NJU!
>
>> We are currently diagnosing network issues on our mirror site. The classic
>> architecture - Nginx (serving static frontend, HTTPS, and caching) -> Apache
>> (reverse proxy + CGI execution) -> cgit / git-http-backend - appears to be
>> functional in principle.
>> The clone failures with large Git repositories are likely caused by
>> insufficient or inappropriate parameter configurations rather than the
>> architecture itself.
> Agreed, it is very likely that the transmission problem is caused by the
> large size of the warehouse.
>
>> P.S., I am the mentor of HUST OpenAtom Club, and our club is maintaining the
>> hust mirror site.
> Thanks very much.

Re: [PATCH] docs/zh_CN: add docs-next checkout workaround

[Weijie Yuan]

On Sun, Jul 12, 2026 at 04:35:21PM +0800, Dongliang Mu wrote:
> > GIT_TRACE=1 \
> > GIT_TRACE_CURL=1 \
> > GIT_CURL_VERBOSE=1 \
> > git clone https://mirror.nju.edu.cn/git/kernel-doc-zh.git/
> > 
> > [...many verbose outputs]
> > remote: Enumerating objects: 11675982, done.
> > remote: Counting objects: 100% (11675982/11675982), done.
> > remote: Compressing objects: 100% (2008049/2008049), done.
> > 13:24:10.505880 http.c:994              == Info: HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
> > 13:24:10.505973 http.c:994              == Info: Connection #0 to host mirror.nju.edu.cn left intact
> > error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
> > error: 6191 bytes of body are still expected
> > fetch-pack: unexpected disconnect while reading sideband packet
> > fatal: early EOF
> > fatal: fetch-pack: invalid index-pack output
> 
> It seems like the same issue with our mirror site. I've forward this email
> thread to NJU mirror maintainers.

Very much appreciated. They might obtain more useful information from
their server logs.

> 
> 
> >  From the output, it seems that there was an error in the mirror of NJU's
> > nginx, the Git HTTP backend behind nginx, or the upstream connection
> > between them, but I'm not 100% sure.
> > 
> > I will conduct several more tests immediately to troubleshoot the
> > problem, to see where exactly the problem lies.
> > 
> > In addition, cloning with a cloud server in Hong Kong:
> > 
> > Cloning into 'kernel-doc-zh'...
> > remote: Enumerating objects: 11675982, done.
> > remote: Counting objects: 100% (11675982/11675982), done.
> > remote: Compressing objects: 100% (2008049/2008049), done.
> > error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
> > error: 3965 bytes of body are still expected
> > fetch-pack: unexpected disconnect while reading sideband packet
> > fatal: early EOF
> > fatal: fetch-pack: invalid index-pack output
> 
> 
> I tried the NJU mirror in my laptop, and successfully clone the repository
> from NJU mirror. There must exist some unknown reason to lead to this
> failure.

Ah, I'm starting to doubt on my side now...

Anyway, I'll check again.

Thanks!