Or little computing tricks and hacks
May 17, 2013Posted by on
The behaviour of the version 2.0 of git will changed for git push/pull.
Before, the default was matching:
matching – push all branches having the same name in both
ends. This is for those who prepare all the branches into a
publishable shape and then push them out with a single command.
It is not appropriate for pushing into a repository shared by
multiple users, since locally stalled branches will attempt a
non-fast forward push if other users updated the branch.
After 2.0, the new default is simple:
simple – like upstream, but refuses to push if the upstream
branch’s name is different from the local one. This is the
safest option and is well-suited for beginners.
Before but close to version 2.0. the user will get a message about this issue everytime that git pull/push is ran:
$ git push warning: push.default is unset; its implicit value is changing in Git 2.0 from 'matching' to 'simple'. To squelch this message and maintain the current behavior after the default changes, use: git config --global push.default matching To squelch this message and adopt the new behavior now, use: git config --global push.default simple See 'git help config' and search for 'push.default' for further information. (the 'simple' mode was introduced in Git 1.7.11. Use the similar mode 'current' instead of 'simple' if you sometimes use older versions of Git) Everything up-to-date
So as the message states and for the sake of repetition, to keep the pre 2.0 behaviour use:
git config --global push.default matching
To adopt the new behaviour use:
git config --global push.default simple
The latter is recommended when the repository is shared and for beginners.