当 git pull 失败时
λ git pull remote: Enumerating objects: 3, done. remote: Counting objects: 100% (3/3), done. remote: Compressing objects: 100% (3/3), done. error: RPC failed; curl 18 transfer closed with outstanding read data remaining fatal: the remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed
repo URL: 'master' must be absolute or begin with ./|../
这一错误出现在 我添加子模块 时，以后再复现，解决
E:\>git push origin master error: src refspec master does not match any error: failed to push some refs to 'email@example.com:Name/repo.git'
git push origin gh-pages
当 https 连接被误以为 ssh 连接时
git push fatal: HttpRequestException encountered 输入 GitHub 用户名 输入 GitHub 密码 成功推送
fatal: refusing to merge unrelated histories
The “fatal: refusing to merge unrelated histories” Git error occurs when two unrelated projects are merged (i.e., projects that are not aware of each other’s existence and have mismatching commit histories).
Consider the following two cases that throw this error:
- You have cloned a project and, somehow, the
.gitdirectory got deleted or corrupted. This leads Git to be unaware of your local history and will, therefore, cause it to throw this error when you try to push to or pull from the remote repository.
- You have created a new repository, added a few commits to it, and now you are trying to pull from a remote repository that already has some commits of its own. Git will also throw the error in this case, since it has no idea how the two projects are related.
The error is resolved by toggling the allow-unrelated-histories switch. After a
git pull or
git merge command, add the following tag:
git pull origin master --allow-unrelated-histories
More information can be found here, on Git’s official documentation.
git push origin master 后出现：
$ git push origin master kex_exchange_identification: read: Connection reset by peer Connection reset by 220.127.116.11 port 22 fatal: Could not read from remote repository.