summaryrefslogtreecommitdiff
path: root/test-dump-cache-tree.c
diff options
context:
space:
mode:
authorLibravatar Lex Spoon <lex@lexspoon.org>2015-04-20 11:00:20 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2015-04-20 12:36:00 -0700
commit96b2d54aeeda3af3775f571a0ab706e6f3678d7a (patch)
tree4a0c8931bff81df138c8b46c324edc185803b490 /test-dump-cache-tree.c
parentRevert "merge: pass verbosity flag down to merge-recursive" (diff)
downloadtgif-96b2d54aeeda3af3775f571a0ab706e6f3678d7a.tar.xz
git-p4: use -m when running p4 changes
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 <lex@lexspoon.org> Acked-by: Luke Diamand <luke@diamand.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'test-dump-cache-tree.c')
0 files changed, 0 insertions, 0 deletions