Re: [PATCH v3] git-p4: Use -m when running p4 changes

2015-04-20 Thread Lex Spoon
On Mon, Apr 20, 2015 at 5:53 AM, Luke Diamand 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 fails with this

Re: [PATCH v3] git-p4: Use -m when running p4 changes

2015-04-20 Thread Luke Diamand
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 Spoo

[PATCH v3] git-p4: Use -m when running p4 changes

2015-04-17 Thread Lex Spoon
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 Reviewed-by: Junio C Hamano Review