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

git-p4 runs out of memory

From
TTTommy Thorn <tt1729@yahoo.com>
Date
Feb 1, 2008, 01:18 UTC
Message-ID
<565265.29093.qm@web39507.mail.mud.yahoo.com>

Trying to survive in a heavily Perforce dominated world, git-p4 looked like the perfect antidote. Unfortunately I have a few problems:

0. git-p4 swells until it runs out of virtual space!
It
   appears that the scripts tries to read everything 
   into memory:
 filedata = p4CmdList('-x - print',
                      stdin='\n'.join(['%s#%s' %
(f['path'], f['rev'])
                                       for f in
files]),
                      stdin_mode='w+')
  Short of rewriting git-p4, is it possible to clone
in
  multiple steps?
1. Short of full Perforce client support, support of 
   exclusion would have helped. Dmitry Kakurin
provided
   a good start. I'll try to generalize it such that
   multiple exclusion can be specified as 
     -//branch/file/blah
2. Having "git p4 commit" be an alias of 
   "git p4 submit" seems a mistake - this is not a 
   commit like a git commit, but more like a git push.

Thanks Tommy

      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 
Message 1 of 1 in “git-p4 runs out of memory”
  1. Tommy ThornFeb 1, 2008

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.