On 18/04/15 00:11, Lex Spoon wrote:
Simply running p4 changes on a large branch can
result in a too many rows scanned error from the
Perforce server. It is better to use a sequence
of smaller calls to p4 changes, using the -m
option to limit the size of each call.
Signed-off-by: Lex Spoon
On Mon, Apr 20, 2015 at 5:53 AM, Luke Diamand l...@diamand.org wrote:
I could be wrong about this, but it looks like importNewBranches() is taking
an extra argument, but that isn't reflected in the place where it gets
called. I think it just got missed.
As a result, t9801-git-p4-branch.sh
Simply running p4 changes on a large branch can
result in a too many rows scanned error from the
Perforce server. It is better to use a sequence
of smaller calls to p4 changes, using the -m
option to limit the size of each call.
Signed-off-by: Lex Spoon l...@lexspoon.org
Reviewed-by: Junio C
3 matches
Mail list logo
