详解git仓库迁移的两种解决方案

 GIT-CLONE(1)      Git Manual      GIT-CLONE(1) NAME git-clone - Clone a repository into a new directory SYNOPSIS git clone [--template=] [-l] [-s] [--no-hardlinks] [-q] [-n] [--bare] [--mirror] [-o ] [-b ] [-u ] [--reference ] [--depth ] [--recursive] [--]  [] --bare Make a bare GIT repository. That is, instead of creating  and placing the administrative files in /.git, make the  itself the $GIT_DIR. This obviously implies the -n because there is nowhere to check out the working tree. Also the branch heads at the remote are copied directly to corresponding local branch heads, without mapping them to refs/remotes/origin/. When this option is used, neither remote-tracking branches nor the related configuration variables are created. git push --mirror --mirror Instead of naming each ref to push, specifies that all refs under refs/ (which includes but is not limited to refs/heads/, refs/remotes/, and refs/tags/) be mirrored to the remote repository. Newly created local refs will be pushed to the remote end, locally updated refs will be force updated on the remote end, and deleted refs will be removed from the remote end. This is the default if the configuration option remote..mirror is set. 

 git clone --bare git://192.168.10.XX/git_repo/project_name.git

 su - git cd /path/to/path/ mkdir new_project_name.git git init --bare new_project_name.git

 cd project_name.git git push --mirror git@192.168.20.XX/path/to/path/new_project_name.git

 cd .. rm -rf project_name.git

 git clone git@192.168.20.XX/path/to/path/new_project_name.git

 git branch -r

 git remote set-url origin remote_git_address