From: Pete Wyckoff <pw@padd.com>
To: Vitor Antunes <vitor.hda@gmail.com>
Cc: git@vger.kernel.org, ggibons@perforce.com
Subject: Re: [PATCHv2 2/2] git p4: add support for 'p4 move' in P4Submit
Date: Mon, 5 Nov 2012 12:57:24 -0500 [thread overview]
Message-ID: <20121105175724.GB889@padd.com> (raw)
In-Reply-To: <loom.20121105T183530-627@post.gmane.org>
vitor.hda@gmail.com wrote on Mon, 05 Nov 2012 17:37 +0000:
> Pete Wyckoff <pw <at> padd.com> writes:
>
> >
> > From: Gary Gibbons <ggibbons <at> perforce.com>
> >
> > For -M option (detectRenames) in P4Submit, use 'p4 move' rather
> > than 'p4 integrate'. Check Perforce server for exisitence of
> > 'p4 move' and use it if present, otherwise revert to 'p4 integrate'.
> >
>
> Hi Pete,
>
> I've just been hit by a situation where this command is available but is
> disabled in the server. I don't know what is the best approach to avoid
> this issue.
Really? The command exists in the server because it returns the
text output for "p4 help move". But "p4 move" itself fails
because it is somehow disabled in the server?
I didn't even know it was possible to administratively disable
commands.
What's the actual error message? And versions of your client and
server (p4 -V, p4d -V, p4 info).
Any ideas Gary?
-- Pete
next prev parent reply other threads:[~2012-11-05 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 23:28 [PATCHv2 0/2] git p4: use "move" command for renames Pete Wyckoff
2012-07-12 23:28 ` [PATCHv2 1/2] git p4: refactor diffOpts calculation Pete Wyckoff
2012-07-12 23:29 ` [PATCHv2 2/2] git p4: add support for 'p4 move' in P4Submit Pete Wyckoff
2012-11-05 17:37 ` Vitor Antunes
2012-11-05 17:57 ` Pete Wyckoff [this message]
2012-11-07 21:06 ` Vitor Antunes
2012-11-11 22:52 ` [PATCH] git p4: handle servers without move support Pete Wyckoff
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=20121105175724.GB889@padd.com \
--to=pw@padd.com \
--cc=ggibons@perforce.com \
--cc=git@vger.kernel.org \
--cc=vitor.hda@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.
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).