Git-related error Summary

Git-related error Summary

 

Garbled Chinese characters entered by the ls command in git

In Git Bash, enterLs commandTo properly display the Chinese file name, you only need to add a line in the file etc \ git-completion.bash under the git installation directory

alias ls='ls --show-control-chars --color=auto'

 

Git push error: warning: push. default is unset

The 'matching 'parameter is the default behavior of Git 1.x. It means that if you execute git push but do not specify a branch, it will push all your local branches to the matched branches in the remote repository. Git 2.x is simple by default, which means that when no branch is specified for executing git push, only the current branch will be pushed to the code you obtained using git pull.

Modify the behavior of git push as prompted: git config -- global push. default matching. Execute git push again to solve the problem.

Pipi Blog

Error "pathspec 'branch' did not match any file (s) known to git ."

 

git checkout mastergit pullgit checkout new_branch

 

An error occurs when git submits a large file.
Error: RPC failed; result = 22, HTTP code = 411
Fatal: The remote end hung up unexpectedly
Fatal: The remote end hung up unexpectedly
Everything up-to-date
In this case, first change the git transmission byte limit.
Git config http. postBuffer 524288000

Another error may occur during transmission at this time.
Error: RPC failed; result = 22, HTTP code = 413
Fatal: The remote end hung up unexpectedly
Fatal: The remote end hung up unexpectedly
Everything up-to-date
These two errors look similar. One is 411, and the other is 413.
Add the key following this error.
First, key-keygen generates the key, and then copies the generated key to the corresponding location under your account in git.

git push ssh://192.168.64.250/eccp.git branch

from:http://blog.csdn.net/pipisorry/article/details/46958699

Ref: solves git Chinese garbled characters