@matheusbsbs / matheus-bagliano / commits / aa064743fa
Fork 0

git-push: Update documentation to describe the no-refspec behavior.

It turns out that the git-push documentation didn't describe what it would do when not given a refspec, (not on the command line, nor in a remotes file). This is fairly important for the user who is trying to understand operations such as: git clone git://something/some/where # hack, hack, hack git push origin I tracked the mystery behavior down to git-send-pack and lifted the relevant portion of its documentation up to git-push, (namely that all refs existing both locally and remotely are updated). Signed-off-by: Carl Worth <cworth@cworth.org> Signed-off-by: Junio C Hamano <junkio@cox.net>

Carl Worth committed Feb 21, 2006 at 20:28 UTC aa064743fa69e2806d5e0af1fab103baa6fa57cd
1 file changed +6
Documentation/git-push.txt
+6
@@ -43,6 +43,12 @@ to fast forward the remote ref that matches <dst>. If
43 the optional plus `+` is used, the remote ref is updated
44 even if it does not result in a fast forward update.
45 +
46 +Note: If no explicit refspec is found, (that is neither
47 +on the command line nor in any Push line of the
48 +corresponding remotes file---see below), then all the
49 +refs that exist both on the local side and on the remote
50 +side are updated.
51 ++
52 Some short-cut notations are also supported.
53 +
54 * `tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.