From: Thomas Berg <merlin66b@gmail.com>
To: Lance Linder <llinder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-p4 move/delete errors
Date: Fri, 9 Jul 2010 17:05:26 +0200 [thread overview]
Message-ID: <AANLkTikPHJuf5JUe096BWTWO_oF9u3gNlVNuw7Ik32WQ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinN0Av1CO7mZU-QKeApq43UmEykUV093eyTtKQN@mail.gmail.com>
Hi,
On Fri, May 28, 2010 at 2:30 AM, Lance Linder <llinder@gmail.com> wrote:
> Until recently I have been successfully using git-p4 with much joy and
> happiness. Then suddenly git-p4 submit started throwing "Command
> failed: p4 diff -du ..." when ever I delete or move a file.
>
> We recently upgraded our perforce server ( Rev.
> P4D/NTX86/2009.2/238357 (2010/03/15) ). It was about this time that
> the problem came up. First thing I did of course was upgrade to the
> latest version of git ( now on 1.7.1 ) but the problem still persists.
> Next I updated my p4 client ( Rev. P4/MACOSX104U/2009.2/238357
> (2010/03/15) ) but still same problem. All other submits work fine as
> long as there are not any deletions or moves.
[...]
>
> Anyone else seeing these issues?
Indeed, we just upgraded our Perforce server too, and now I'm getting
this exact error. Did you find a solution to the problem?
If not I'm very interested in solving it. Seems like the p4 diff
command has changed behaviour and broken the git-p4 script.
Cheers,
Thomas
next prev parent reply other threads:[~2010-07-09 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 0:30 git-p4 move/delete errors Lance Linder
2010-07-09 15:05 ` Thomas Berg [this message]
2010-07-09 17:06 ` Lance Linder
2010-07-09 20:21 ` Tor Arvid Lund
2010-07-09 21:20 ` Lance Linder
2010-07-09 21:32 ` Thomas Berg
2010-07-13 11:22 ` Thomas Berg
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=AANLkTikPHJuf5JUe096BWTWO_oF9u3gNlVNuw7Ik32WQ@mail.gmail.com \
--to=merlin66b@gmail.com \
--cc=git@vger.kernel.org \
--cc=llinder@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).