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

git p4 submit always tries to re-apply every patch

From
Tthussvm <thuss@volunteermatch.org>
Date
Dec 2, 2010, 02:30 UTC
Message-ID
<1291257039313-5794578.post@n2.nabble.com>

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.
Next: Tor Arvid Lund
Message 1 of 2 in “git p4 submit always tries to re-apply every patch”
  1. thussvmDec 2, 2010
  2. Tor Arvid LundDec 2, 2010

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.