]> git.ipfire.org Git - thirdparty/git.git/commit - git-p4.py
projects / thirdparty / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3d6bc9a) | patch
git-p4: use -m when running p4 changes
authorLex Spoon <lex@lexspoon.org>
Mon, 20 Apr 2015 15:00:20 +0000 (11:00 -0400)
committerJunio C Hamano <gitster@pobox.com>
Mon, 20 Apr 2015 19:36:00 +0000 (12:36 -0700)
commit96b2d54aeeda3af3775f571a0ab706e6f3678d7a
tree4a0c8931bff81df138c8b46c324edc185803b490tree | snapshot
parent3d6bc9a763f56156b424e7382b4029a67a49847ecommit | diff
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>
Documentation/git-p4.txt diff | blob | blame | history
git-p4.py diff | blob | blame | history
t/t9818-git-p4-block.sh [new file with mode: 0755] blob
Unnamed repository; edit this file 'description' to name the repository.