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
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
