From: Luke Diamand <luke@diamand.org>
To: Igor Kushnir <igorkuo@gmail.com>
Cc: Git Users <git@vger.kernel.org>,
Lars Schneider <larsxschneider@gmail.com>,
Ori Rawlings <orirawlings@gmail.com>
Subject: Re: [PATCH] git-p4: do not pass '-r 0' to p4 commands
Date: Thu, 29 Dec 2016 09:20:27 +0000 [thread overview]
Message-ID: <CAE5ih78HgKMOgXC82eTC3j-ehLmPXmNd0jQPJLcZebFXhWxOLQ@mail.gmail.com> (raw)
In-Reply-To: <20161229090533.4717-1-igorkuo@gmail.com>
On 29 December 2016 at 09:05, Igor Kushnir <igorkuo@gmail.com> wrote:
> 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.
That looks like a good fix, thanks.
I feel sad for anyone still using 2012.1.
Luke
>
> Signed-off-by: Igor Kushnir <igorkuo@gmail.com>
> ---
> Documentation/git-p4.txt | 1 +
> git-p4.py | 4 +++-
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/git-p4.txt b/Documentation/git-p4.txt
> index bae862ddc..f4f1be5be 100644
> --- a/Documentation/git-p4.txt
> +++ b/Documentation/git-p4.txt
> @@ -479,6 +479,7 @@ 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.
> + '-r 0' is not passed to p4 commands if this option is set to 0.
>
> Clone and sync variables
> ~~~~~~~~~~~~~~~~~~~~~~~~
> diff --git a/git-p4.py b/git-p4.py
> index 22e3f57e7..e5a9e1cce 100755
> --- a/git-p4.py
> +++ b/git-p4.py
> @@ -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
> --
> 2.11.0
>
next prev parent reply other threads:[~2016-12-29 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 9:05 [PATCH] git-p4: do not pass '-r 0' to p4 commands Igor Kushnir
2016-12-29 9:20 ` Luke Diamand [this message]
2016-12-29 10:02 ` Lars Schneider
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAE5ih78HgKMOgXC82eTC3j-ehLmPXmNd0jQPJLcZebFXhWxOLQ@mail.gmail.com \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=igorkuo@gmail.com \
--cc=larsxschneider@gmail.com \
--cc=orirawlings@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).