Trying to move an SVN repository to git, I discovered a couple of interesting facts:<\/p>\n
It only copies one branch, so the resulting repository is not identical to the original. Creating a real clone with all branches is possible, but it requires adding a local branch for each remote branch:<\/p>\n Beware of counterfeits: if you do As far as I can tell, there is no way to tell “pull” to pull all branches, as well as there is no way to tell “push” to push to all remotes.<\/p>\n git pull does not remove references to deleted remote branches<\/b><\/p>\n Let’s say you pulled a branch Fun stuff!<\/p>\n","protected":false},"excerpt":{"rendered":" Trying to move an SVN repository to git, I discovered a couple of interesting facts: git clone does not really clone. It only copies one branch, so the resulting repository […]<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"Layout":"","footnotes":""},"categories":[21],"tags":[],"class_list":["entry","author-ikriv","post-1637","post","type-post","status-publish","format-standard","category-git"],"_links":{"self":[{"href":"https:\/\/ikriv.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1637","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ikriv.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ikriv.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ikriv.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ikriv.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1637"}],"version-history":[{"count":0,"href":"https:\/\/ikriv.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1637\/revisions"}],"wp:attachment":[{"href":"https:\/\/ikriv.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1637"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ikriv.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1637"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ikriv.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1637"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}git clone<\/a><\/code> does not really clone<\/b>.<\/p>\nbranch --track somename origin\/somename<\/code><\/p>\nbranch --track somename (bad)<\/font><\/code> or branch -track origin\/somename origin\/somename (bad)<\/font><\/code>, this won’t do what you want. Also, you will get an error if you will try to track an already tracked branch like master<\/code>.<\/p>\ngit pull --all<\/a><\/code> and git push --all<\/a><\/code> are not symmetrical<\/b><\/p>\ngit pull --all<\/code> means “all remotes”. It pulls a single branch from all remotes (and it looks like it pulls tags as well). A typical repository has exactly one remote called “origin”.<\/p>\ngit push --all<\/code> means “all branches”. It pushes all branches to a single remote. To add to the confusion, it does not push tags.<\/p>\nfoo<\/code> from origin, and then someone else deleted it from the remote repository. Your local repository will still have a dangling reference to origin\/foo<\/code>. Pulling from origin does not change anything. To get rid of the dangling reference you must cast a special spell:<\/p>\ngit remote prune origin<\/code><\/p>\n