[FFmpeg-cvslog] doc/git-howto: Replace "git push" example by one with dry-run

Michael Niedermayer git at videolan.org
Mon Aug 3 19:43:59 CEST 2015


ffmpeg | branch: master | Michael Niedermayer <michael at niedermayer.cc> | Mon Aug  3 11:56:31 2015 +0200| [2ca0ed9cfda21c8a6f9884b93613602782dcda71] | committer: Michael Niedermayer

doc/git-howto: Replace "git push" example by one with dry-run

I do not think having "git push" as example is a good idea.
The command has a very high chance of pushing things which are unwanted to be
pushed

Reviewed-by: Carl Eugen Hoyos <cehoyos at ag.or.at>
Signed-off-by: Michael Niedermayer <michael at niedermayer.cc>

> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=2ca0ed9cfda21c8a6f9884b93613602782dcda71
---

 doc/git-howto.texi |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/git-howto.texi b/doc/git-howto.texi
index b7b5d43..b3c8ff0 100644
--- a/doc/git-howto.texi
+++ b/doc/git-howto.texi
@@ -326,10 +326,12 @@ faulty commit disappear from the history.
 @section Pushing changes to remote trees
 
 @example
-git push
+git push origin master --dry-run
 @end example
 
-Will push the changes to the default remote (@var{origin}).
+Will simulate a push of the local master branch to the default remote
+(@var{origin}). And list which branches and ranges or commits would have been
+pushed.
 Git will prevent you from pushing changes if the local and remote trees are
 out of sync. Refer to @ref{Updating the source tree to the latest revision}.
 



More information about the ffmpeg-cvslog mailing list