summaryrefslogtreecommitdiff
path: root/resolve-undo.c
diff options
context:
space:
mode:
authorLex Spoon <lex@lexspoon.org>2015-04-20 15:00:20 (GMT)
committerJunio C Hamano <gitster@pobox.com>2015-04-20 19:36:00 (GMT)
commit96b2d54aeeda3af3775f571a0ab706e6f3678d7a (patch)
tree4a0c8931bff81df138c8b46c324edc185803b490 /resolve-undo.c
parent3d6bc9a763f56156b424e7382b4029a67a49847e (diff)
downloadgit-96b2d54aeeda3af3775f571a0ab706e6f3678d7a.zip
git-96b2d54aeeda3af3775f571a0ab706e6f3678d7a.tar.gz
git-96b2d54aeeda3af3775f571a0ab706e6f3678d7a.tar.bz2
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 'resolve-undo.c')
0 files changed, 0 insertions, 0 deletions