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

Re: Cannot fetch whole history from Perforce

From
TBThomas Berg <merlin66b@gmail.com>
Date
Mar 8, 2011, 20:36 UTC
Message-ID
<AANLkTin6BBD+b2OYRk32GyAaEqFa-V7T1B7jEVujRkuL@mail.gmail.com>
In-Reply-To
<AANLkTik6fxHUJbp6dWdAgV-wr=P=FxK1K-vGAGy8ruBd@mail.gmail.com>
Hi,
On Tue, Mar 8, 2011 at 7:09 PM, Anatol Pomozov <anatol.pomozov@gmail.com> wrote:
Show 7 quoted lines
> Hi, I am using HEAD version of the git and I have an issue with git-p4
> tool (p4 to git importer).
>
> git-p4 works fine when I import HEAD version of my project
>
> $ git p4 clone //depot/foo/bar --verbose
> But it fails with a cryptic error when I try to import @all revisions:
[...]
>
> $ git p4 clone //depot/foo/bar@all --verbose
> Importing from //depot/foo/bar@all into bar
[...]
>
> Can it be related to Pete's changes?
> http://permalink.gmane.org/gmane.comp.version-control.git/167281

Sorry for not testing myself before responding, but in my experience with Perforce a trailing slash may be significant. Did you try this format? $ git p4 clone //depot/foo/bar/@all If that also fails you may be onto something.

- Thomas
Previous: Anatol PomozovNext: Tor Arvid Lund
Message 2 of 4 in “Cannot fetch whole history from Perforce”
  1. Anatol PomozovMar 8, 2011
  2. Thomas BergMar 8, 2011
  3. Tor Arvid LundMar 8, 2011
  4. Anatol PomozovMar 12, 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.