git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Push to origin failed

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Jan 19, 2010, 15:05 UTC
Message-ID
<fabb9a1e1001190705o5698e675med65ec8618befa8e@mail.gmail.com>
In-Reply-To
<4B55C48F.2090005@cedarsoft.com>
Heya,

On Tue, Jan 19, 2010 at 15:41, Johannes Schneider <mailings@cedarsoft.com> wrote:

>  ! [rejected]        master -> master (non-fast forward)

There's your problem. You could solve it by instead doing 'git push -f' (telling it to push even though it's not a fast-forward), but that would make it hard for those downstream of that repository. So, read up on 'fast-forwards' and why it's bad to push if it's not a fast-forward, but mainly figure out why you have a fast-forward in the first place. It could very well be that you need to fetch and merge (or fetch and rebase) first.

-- 
Cheers,

Sverre Rabbelier
Previous: Johannes Schneider
Message 2 of 2 in “Push to origin failed”
  1. Johannes SchneiderJan 19, 2010
  2. Sverre RabbelierJan 19, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.