From: Weijie Yuan <wy@wyuan.org>
To: Dongliang Mu <dzm91@hust.edu.cn>
Cc: Siwei Chen <businiaoanka@anka1.top>,
linux-doc@vger.kernel.org, si.yanteng@linux.dev
Subject: Re: Issue cloning kernel-doc-zh from HUST mirror
Date: Tue, 23 Jun 2026 20:01:11 +0800 [thread overview]
Message-ID: <ajp1h-RdbmQ43yio@wyuan.org> (raw)
In-Reply-To: <b03f244b-46b8-47e8-b7f5-d98d714ae15c@hust.edu.cn>
On Tue, Jun 23, 2026 at 04:51:20PM +0800, Dongliang Mu wrote:
> The curl 52 Empty reply from server error is not a Git or Ubuntu
> compatibility issue. It happens because the kernel-doc-zh repository is
> extremely large, and the HUST mirror server closes the HTTPS connection
> early due to timeout or proxy limits.
>
> You can try the following commands:
>
> 1. Shallow clone first (most reliable)
>
> git clone --depth 1
> https://mirrors.hust.edu.cn/git/kernel-doc-zh.git linux
>
> Then fetch full history:
>
> git fetch --unshallow
>
> If still failing, increase Git buffer like:
>
> git config --global http.postBuffer 1073741824
>
> Finally, I will contact maintainers of HUST mirror site and try
> some attempts to resolve this issue.
Thanks, and yes, shallow clone could work:
user@debian:~$ git clone --depth 1 https://mirrors.hust.edu.cn/git/kernel-doc-zh.git linux
Cloning into 'linux'...
remote: Enumerating objects: 93130, done.
remote: Counting objects: 100% (93130/93130), done.
remote: Compressing objects: 100% (90511/90511), done.
remote: Total 93130 (delta 7145), reused 20322 (delta 1615), pack-reused 0
Receiving objects: 100% (93130/93130), 259.15 MiB | 4.71 MiB/s, done.
Resolving deltas: 100% (7145/7145), done.
Updating files: 100% (87897/87897), done.
But:
user@debian:~$ cd linux
user@debian:~/linux$ git fetch --unshallow
(after ~10 minutes or so)
remote: Enumerating objects: 10638034, done.
remote: Counting objects: 100% (10638019/10638019), done.
remote: Compressing objects: 100% (1819658/1819658), done.
error: RPC failed; curl 56 GnuTLS recv error (-9): Error decoding the received TLS packet.
error: 5476 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
and in a mac (26.5.1) Git 2.54, probably the same:
$ git clone https://mirrors.hust.edu.cn/git/kernel-doc-zh.git linux
Cloning into 'linux'...
remote: Enumerating objects: 11406904, done.
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
error: 7537 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
after setting http.postBuffer 1073741824 on debian:
user@debian:~/linux$ git config --global http.postBuffer 1073741824
user@debian:~/linux$ git fetch --unshallow
(after ~10 minutes)
remote: Enumerating objects: 10638034, done.
remote: Counting objects: 100% (10638019/10638019), done.
remote: Compressing objects: 100% (1819658/1819658), done.
error: RPC failed; curl 56 GnuTLS recv error (-9): Error decoding the received TLS packet.
error: 5917 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
Apparently the above is of limited value, as it is straightforward to
reproduce.
> Please use the first git repo:
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/alexs/linux.git
The average speed of cloning from git.kernel.org is less than 10 KiB/s
from Chengdu ;-)
But of course, a shallow clone is enough for translation work ;-)
Thanks!
prev parent reply other threads:[~2026-06-23 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 7:39 Issue cloning kernel-doc-zh from HUST mirror Siwei Chen
2026-06-23 8:25 ` Dongliang Mu
2026-06-23 8:51 ` Dongliang Mu
2026-06-23 10:04 ` Siwei Chen
2026-06-23 12:01 ` 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=ajp1h-RdbmQ43yio@wyuan.org \
--to=wy@wyuan.org \
--cc=businiaoanka@anka1.top \
--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