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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html