On 07/06/15 17:01, Lex Spoon wrote:
Great work.
Thanks! I actually found the problem in my day job, so it was very handy
having all the infrastructure already in place!
For curiosity's sake, the -m solution has been observed to work on at
least one Perforce installation. However clearly it d
Great work.
For curiosity's sake, the -m solution has been observed to work on at
least one Perforce installation. However clearly it doesn't work on
others, so the batch ranges approach looks like it will be better.
Based on what has been seen so far, the Perforce maxscanrows setting
must be app
We recently added support to git-p4 to limit the number of changes it
would try to import at a time. That was to help clients who were being
limited by the "maxscanrows" limit. This used the "-m maxchanges"
argument to "p4 changes" to limit the number of results returned to
git-p4.
Unfortunately i
3 matches
Mail list logo
