Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The same question exists for mercurial, and I’m wondering how this applies to git? In particular, I’m interested in cases where there are two local repos, and copying between servers using rsync or such.
Also, if the original repo is itself cloned from, say gitorious, and I copy it, then gitorious will still exist as a remote (tracked by the master branch) in the copy, right? Does this happen if the copy is cloned instead?
Cloning a repository gives you a copy of that repository and configures the original repository as a remote.
Copying a repository just gives you a copy of that repository. (Though you can of course just add the remote definition afterwards via
git remote add.)Copying a repository copies its
.git/configfile, and thus its remotes. Cloning a repository does not copy the config file, and thus the remotes are not shared. (The repository that was cloned from is set as theoriginremote in the resulting clone.)