summaryrefslogtreecommitdiff
path: root/contrib/examples/git-gc.sh
diff options
context:
space:
mode:
authorLibravatar Matthieu Moy <Matthieu.Moy@imag.fr>2013-06-17 19:52:41 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-06-18 07:35:48 -0700
commit70495b556f5685afe0e41988e42d48b2331d77a0 (patch)
treef298d319d39c85c5b93913a25513106c7dad53dd /contrib/examples/git-gc.sh
parentfast-export: fix argument name in error messages (diff)
downloadtgif-70495b556f5685afe0e41988e42d48b2331d77a0.tar.xz
Documentation/git-push.txt: explain better cases where --force is dangerous
The behavior of "git push --force" is rather clear when it updates only one remote ref, but running it when pushing several branches can really be dangerous. Warn the users a bit more and give them the alternative to push only one branch. Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/examples/git-gc.sh')
0 files changed, 0 insertions, 0 deletions