git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: thussvm <thuss@volunteermatch.org>
To: git@vger.kernel.org
Subject: git p4 submit always tries to re-apply every patch
Date: Wed, 1 Dec 2010 18:30:39 -0800 (PST)	[thread overview]
Message-ID: <1291257039313-5794578.post@n2.nabble.com> (raw)


Whenever I run a git p4 submit after a git pull from the origin it tries to
re-apply every commit, even ones that were already submitted previously
(which results in self generated conflicts). What's interesting is that this
works:

git p4 submit <--- submit some changes
git p4 submit <--- no changes to submit, so it recognizes that it's up to
date

but as soon as I throw in a git pull origin master (even if there is nothing
new on the origin) it loses track and on the next submit it tries to
re-apply EVERYTHING. For example:

git p4 submit <--- no changes to submit
git pull origin master <--- no activity on the git server side so no changes
applied
git p4 submit <--- tries to re-apply all changes that were already submitted
earlier

Is git pull origin master somehow wiping out git p4's notion of which
changes have been applied and which haven't?
-- 
View this message in context: http://git.661346.n2.nabble.com/git-p4-submit-always-tries-to-re-apply-every-patch-tp5794578p5794578.html
Sent from the git mailing list archive at Nabble.com.

             reply	other threads:[~2010-12-02  2:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02  2:30 thussvm [this message]
2010-12-02  9:36 ` git p4 submit always tries to re-apply every patch Tor Arvid Lund

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=1291257039313-5794578.post@n2.nabble.com \
    --to=thuss@volunteermatch.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).