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

Re: git-p4 move/delete errors

From
TBThomas Berg <merlin66b@gmail.com>
Date
Jul 9, 2010, 15:05 UTC
Message-ID
<AANLkTikPHJuf5JUe096BWTWO_oF9u3gNlVNuw7Ik32WQ@mail.gmail.com>
In-Reply-To
<AANLkTinN0Av1CO7mZU-QKeApq43UmEykUV093eyTtKQN@mail.gmail.com>
Hi,
On Fri, May 28, 2010 at 2:30 AM, Lance Linder <llinder@gmail.com> wrote:
Show 11 quoted lines
> 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

Previous: Lance LinderNext: Lance Linder
Message 2 of 7 in “git-p4 move/delete errors”
  1. Lance LinderMay 28, 2010
  2. Thomas BergJul 9, 2010
  3. Lance LinderJul 9, 2010
  4. Tor Arvid LundJul 9, 2010
  5. Lance LinderJul 9, 2010
  6. Thomas BergJul 9, 2010
  7. Thomas BergJul 13, 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.