On 12/13/2013 3:44 PM, Mathias Gaunard wrote:
On 09/12/2013 01:48, Edward Diener wrote:
On 12/8/2013 6:18 PM, Mathias Gaunard wrote:
On 09/12/2013 00:00, Edward Diener wrote:
The result is:
Pushing to https://github.com/eldiener/mplsun.git To https://github.com/eldiener/mplsun.git ! [rejected] suncc -> master (non-fast-forward) error: failed to push some refs to 'https://github.com/eldiener/mplsun.git' hint: Updates were rejected because a pushed branch tip is behind its remote hint: counterpart. Check out this branch and merge the remote changes hint: (e.g. 'git pull') before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details
What does it mean that a "pushed branch tip is behind its remote" ? All I am trying to do is 'push' this repository onto an almost entirely empty remote repository. How hard can that be with git ?
You're trying to push the local "suncc" branch to the remote "master" branch. There is already some history in the remote master branch, and your local suncc branch is not a descendant of that history. To prevent history rewriting, git is therefore refusing to branch.
How was I supposed to interpret this reality from "Updates were rejected because a pushed branch tip is behind its remote" <g> ?
I personally find that "non-fast-forward" is pretty explicit.
I have to pick up and understand git terminology. For a relative git novice like me "non-fast forward" sounds like a reference to a recording device <g>. I am studying git to get up to speed. Printed out "Pro Git" and am slowly going through it. I do like how easy it is to create new branches, switch between branches, push and pull branches. But I am sure there is much else I do not know and I have to learn it to be comfortable with how git works.