| commit | 70495b556f5685afe0e41988e42d48b2331d77a0 | |
| author | Matthieu Moy <Matthieu.Moy@imag.fr> | |
| Mon, 17 Jun 2013 17:52:41 +0000 (17 19:52 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 18 Jun 2013 14:35:48 +0000 (18 07:35 -0700) | ||
| tree | f298d319d39c85c5b93913a25513106c7dad53dd | treesnapshot (tar.gz zip) |
| parent | 04a74b6cfa5ef4870263f84ac94a488d9f2ef14a | commitdiff |
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>
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>
| Documentation/git-push.txt | diffblobblamehistory |