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

[PATCH] Add the option to not sync after a submitting to Perforce.

From
BMBenjamin C Meyer <bmeyer@rim.com>
Date
Jun 4, 2010, 17:33 UTC
Message-ID
<1275672784-16371-1-git-send-email-bmeyer@rim.com>

When p4->git syncing occurs not on the users machine, but on a central mirror server there is no local remote. When a user performs a 'git p4 submit' in this configuration after successfully applying the patches the p4 submit command will then output a failure because it could not p4 sync. This causes users to think their submit failed when in fact it was successful.

Signed-off-by: Benjamin C Meyer <bmeyer@rim.com>
---
 contrib/fast-import/git-p4 |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/contrib/fast-import/git-p4 b/contrib/fast-import/git-p4
index d42b865..2a9771b 100755
--- a/contrib/fast-import/git-p4
+++ b/contrib/fast-import/git-p4
@@ -823,6 +823,9 @@ class P4Submit(Command):
             print "All changes applied!"
             chdir(self.oldWorkingDirectory)
 
+            if gitConfig("git-p4.syncAfterSubmit") == "false":
+                return True
+
             sync = P4Sync()
             sync.run([])
 
-- 
1.7.1
Message 1 of 1 in “Add the option to not sync after a submitting to Perforce.”
  1. Add the option to not sync after a submitting to Perforce.Benjamin C Meyer, Jun 4, 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.