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

[PATCH 5/8] git-p4: reinterpret confusing p4 message

From
PWPete Wyckoff <pw@padd.com>
Date
Feb 5, 2011, 22:52 UTC
Message-ID
<20110205225214.GF30963@arf.padd.com>
In-Reply-To
<20110205224848.GA30963@arf.padd.com>
Error output will look like this:

glom$ git p4 clone //deopt Importing from //deopt into . Reinitialized existing Git repository in /tmp/x/.git/ Doing initial import of //deopt from revision #head into refs/remotes/p4/master p4 returned an error: //deopt/... - must refer to client glom.

This particular p4 error is misleading. Perhaps the depot path was misspelled. Depot path: //deopt

Signed-off-by: Pete Wyckoff <pw@padd.com>
---
 contrib/fast-import/git-p4 |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/contrib/fast-import/git-p4 b/contrib/fast-import/git-p4
index db19b17..6b847c4 100755
--- a/contrib/fast-import/git-p4
+++ b/contrib/fast-import/git-p4
@@ -1445,6 +1445,10 @@ class P4Sync(Command):
             if 'code' in info and info['code'] == 'error':
                 sys.stderr.write("p4 returned an error: %s\n"
                                  % info['data'])
+                if info['data'].find("must refer to client") >= 0:
+                    sys.stderr.write("This particular p4 error is misleading.\n")
+                    sys.stderr.write("Perhaps the depot path was misspelled.\n");
+                    sys.stderr.write("Depot path:  %s\n" % " ".join(self.depotPaths))
                 sys.exit(1)
             if 'p4ExitCode' in info:
                 sys.stderr.write("p4 exitcode: %s\n" % info['p4ExitCode'])
-- 
1.7.2.3
Previous: Tor Arvid LundNext: Pete Wyckoff
Message 11 of 18 in “git-p4 fixes and enhancements”
  1. 0/8 git-p4 fixes and enhancementsPete Wyckoff, Feb 5, 2011
  2. 1/8 git-p4: test scriptPete Wyckoff, Feb 5, 2011
  3. Vitor AntunesFeb 6, 2011
  4. Junio C HamanoFeb 7, 2011
  5. Pete WyckoffFeb 7, 2011
  6. 2/8 git-p4: fix key error for p4 problemPete Wyckoff, Feb 5, 2011
  7. 3/8 git-p4: add missing newline in initial import messagePete Wyckoff, Feb 5, 2011
  8. Tor Arvid LundFeb 8, 2011
  9. 4/8 git-p4: accommodate new move/delete type in p4Pete Wyckoff, Feb 5, 2011
  10. Tor Arvid LundFeb 8, 2011
  11. 5/8 git-p4: reinterpret confusing p4 messagePete Wyckoff, Feb 5, 2011
  12. 6/8 git-p4: better message for "git-p4 sync" when not clonedPete Wyckoff, Feb 5, 2011
  13. Tor Arvid LundFeb 8, 2011
  14. 7/8 git-p4: decode p4 wildcard charactersPete Wyckoff, Feb 5, 2011
  15. Tor Arvid LundFeb 8, 2011
  16. Pete WyckoffFeb 8, 2011
  17. 8/8 git-p4: support clone --barePete Wyckoff, Feb 5, 2011
  18. Tor Arvid LundFeb 8, 2011

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.