Subject: Re: [boost] [git] Write permission to branch
From: Mathias Gaunard (mathias.gaunard_at_[hidden])
Date: 2013-12-13 15:44:18
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
>>> hint: Updates were rejected because a pushed branch tip is behind its
>>> 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
>>> 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"
>> 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.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk