Git push remote is upset

Well while working merrily away on my project I ran into a snafu while trying to push my get repo to a remote. I am sure this had something to do with updating me updating to Saucy which I am sure updated my git version. Here is the message I encountered.

$ 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)



… scratches head …

$ git help config
-- snip --
       push.default
           Defines the action git push should take if no refspec is given on
           the command line, no refspec is configured in the remote, and no
           refspec is implied by any of the options given on the command line.
           Possible values are:

           ·   nothing - do not push anything.

           ·   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.

               This is currently the default, but Git 2.0 will change the
               default to simple.

           ·   upstream - push the current branch to its upstream branch
               (tracking is a deprecated synonym for this). With this, git
               push will update the same remote ref as the one which is merged
               by git pull, making push and pull symmetrical. See
               "branch..merge" for how to configure the upstream branch.

           ·   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. It will become
               the default in Git 2.0.

           ·   current - push the current branch to a branch of the same name.

           The simple, current and upstream modes are for those who want to
           push out a single branch after finishing work, even when the other
           branches are not yet ready to be pushed out. If you are working
           with other people to push into the same shared repository, you
           would want to use one of these.

$ git config --global push.default simple

Note this is going to update your ~/.gitconfig file and add the following section to it.

[push]
        default = simple

Now all is right with my git world again.

$ git push
Counting objects: 14, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (12/12), done.
Writing objects: 100% (14/14), 113.44 KiB | 0 bytes/s, done.
Total 14 (delta 0), reused 0 (delta 0)
To https://github.com/jsheffie/
 * [new branch]      master -> master