git clone:fatal: 远端意外挂断

声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow 原文地址: http://stackoverflow.com/questions/5279151/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me): StackOverFlow

提示:将鼠标放在中文语句上可以显示对应的英文。显示中英文
时间:2020-09-19 05:11:21  来源:igfitidea点击:

git clone: fatal: The remote end hung up unexpectedly

gitcygwin

提问by Android Eve

I just installed Git, eager to use it for the first time for "cloning" a project, but as soon as I tried my first ever command I receive this dreaded error message:

我刚刚安装了 Git,渴望第一次使用它来“克隆”一个项目,但是当我尝试我的第一个命令时,我收到了这个可怕的错误消息:

fatal: The remote end hung up unexpectedly

致命:远端意外挂断

The command I was trying to run was:

我试图运行的命令是:

 git clone git://android.git.kernel.org/projects/platform/packages/apps/Browser.git/tree

Any idea why I am getting this fail?

知道为什么我会失败吗?

BTW, I am using the latest cygwin 1.7.8 git 1.7.4 on Windows XP SP3 32-bit.

顺便说一句,我在 Windows XP SP3 32 位上使用最新的 cygwin 1.7.8 git 1.7.4。

回答by karlphillip

What you should do instead is:

你应该做的是:

git clone git://android.git.kernel.org/platform/packages/apps/Browser.git

Outputs:

输出

Cloning into Browser...
remote: Counting objects: 10361, done.
remote: Compressing objects: 100% (2394/2394), done.
remote: Total 10361 (delta 5024), reused 10254 (delta 4943)
Receiving objects: 100% (10361/10361), 4.67 MiB | 4.91 MiB/s, done.
Resolving deltas: 100% (5024/5024), done.

回答by Dale Forester

Try export CYGWIN=binmode. I've run into that or a very similar problem. Cygwin sometimes has its issues. It's not perfect. Even after this fix. You need to do that export every login. Consider putting it in /etc/profile.

试试export CYGWIN=binmode。我遇到了那个或非常相似的问题。Cygwin 有时会出现问题。这并不完美。即使在此修复之后。您需要在每次登录时导出。考虑将它放在 /etc/profile 中。

回答by Michael Dausmann

I had a similar problem and solved it by recycling my router. I guess in my case it was some sort of connectivity problem.

我有一个类似的问题,并通过回收我的路由器解决了它。我想就我而言,这是某种连接问题。