From: Martin Fick <mfick@codeaurora.org>
To: Git Mailing List <git@vger.kernel.org>
Subject: Interleaved remote branch update problems
Date: Thu, 5 Apr 2012 15:49:14 -0600 [thread overview]
Message-ID: <201204051549.14397.mfick@codeaurora.org> (raw)
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 reply other threads:[~2012-04-05 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 21:49 Martin Fick [this message]
2012-04-06 0:37 ` Interleaved remote branch update problems Jeff King
2012-04-06 5:32 ` Martin Fick
2012-04-06 6:09 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201204051549.14397.mfick@codeaurora.org \
--to=mfick@codeaurora.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).