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

How can git pull be up-to-date and git push fail?

From
Bill Lear <rael@zopyra.com>
Date
Apr 5, 2007, 12:15 UTC
Message-ID
<17940.59514.150325.738141@lisa.zopyra.com>

I'm trying to explain this behavior to a co-worker, and how to solve it:

% git pull Already up-to-date.

% git push error: remote 'refs/remotes/origin/flexify' is not a strict subset of localref 'refs/remotes/origin/flexify'. maybe you are not up-to-date and need to pull first?

I believe he is using git 1.5.0 and that the above was tried from the master branch.

So, I'm confused: I would have thought the way you solve the problem in step 2 is by executing step 1. Would he need to do this:

% git checkout flexify % git pull flexify:flexify % git checkout master % git push

Bill
Next: Jeff King
Message 1 of 13 in “How can git pull be up-to-date and git push fail?”
  1. Bill LearApr 5, 2007
  2. Jeff KingApr 5, 2007
  3. Bill LearApr 5, 2007
  4. Bill LearApr 5, 2007
  5. Jeff KingApr 5, 2007
  6. Bill LearApr 5, 2007
  7. Jeff KingApr 7, 2007
  8. Junio C HamanoApr 5, 2007
  9. Jeff KingApr 6, 2007
  10. Junio C HamanoApr 6, 2007
  11. Jeff KingApr 7, 2007
  12. Junio C HamanoApr 7, 2007
  13. Jeff KingApr 7, 2007

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.