Skip to contentSkip to conversation

git-p4: do not pass '-r 0' to p4 commands

PATCH In review Igor Kushnir 3 participants 3 messages Dec 29, 2016 – Jan 4, 2017 Documentation

lore
Share & tools
lore

Igor Kushnir

author
#0 lore raw

PATCH v2 1/1 git-p4: do not pass '-r 0' to p4 commands

git-p4 crashes when used with a very old p4 client version that does not support the '-r <number>' option in its commands.

Allow making git-p4 work with old p4 clients by setting git-p4.retries to 0.

Alternatively git-p4.retries could be made opt-in.
But since only very old, barely maintained p4 versions don't support the '-r' option, the setting-retries-to-0 workaround would do.

The "-r retries" option is present in Perforce 2012.2 Command Reference, but absent from Perforce 2012.1 Command Reference.

Signed-off-by Igor Kushnir <[email protected]>
---
 Documentation/git-p4.txt | 2 ++
 git-p4.py                | 4 +++-
 2 files changed, 5 insertions(+), 1 deletion(-)
Documentation/git-p4.txt +2 -0
index bae862ddc..7436c64a9 100644
@@ -479,6 +479,8 @@ git-p4.client::
 git-p4.retries::
 	Specifies the number of times to retry a p4 command (notably,
 	'p4 sync') if the network times out. The default value is 3.
+	Set the value to 0 to disable retries or if your p4 version
+	does not support retries (pre 2012.2).
 
 Clone and sync variables
 ~~~~~~~~~~~~~~~~~~~~~~~~
git-p4.py +3 -1
index 22e3f57e7..7bda915bd 100755
@@ -83,7 +83,9 @@ def p4_build_cmd(cmd):
     if retries is None:
         # Perform 3 retries by default
         retries = 3
-    real_cmd += ["-r", str(retries)]
+    if retries > 0:
+        # Provide a way to not pass this option by setting git-p4.retries to 0
+        real_cmd += ["-r", str(retries)]
 
     if isinstance(cmd,basestring):
         real_cmd = ' '.join(real_cmd) + ' ' + cmd
Signature · 1 line
2.11.0
#2 lore raw
Quoted 1 line · Ori Rawlings

Looks good to me.

And me.

Quoted 3 lines

Ori Rawlings