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

Interleaved remote branch update problems

From
MFMartin Fick <mfick@codeaurora.org>
Date
Apr 5, 2012, 21:49 UTC
Message-ID
<201204051549.14397.mfick@codeaurora.org>

I have noticed that git push --force does not reliably force a push to remote branches. In particular, it will not update a remote branch if that branch has been updated since the beginning of the push. Is this normal, is this expected? It also fails to fast forward in a similar situation without the -f flag. This seems counter intuitive from the perspective of a git push user. Are there good reasons for this?

-Martin
(Using git 1.7.8 or 1.7.10-rc3)
-- 
Employee of Qualcomm Innovation Center, Inc. which is a 
member of Code Aurora Forum
Next: Jeff King
Message 1 of 4 in “Interleaved remote branch update problems”
  1. Martin FickApr 5, 2012
  2. Jeff KingApr 6, 2012
  3. Martin FickApr 6, 2012
  4. Jeff KingApr 6, 2012

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.