diff options
author | Carl Worth <cworth@cworth.org> | 2006-02-21 20:28:50 -0800 |
---|---|---|
committer | Junio C Hamano <junkio@cox.net> | 2006-02-21 22:11:50 -0800 |
commit | aa064743fa69e2806d5e0af1fab103baa6fa57cd (patch) | |
tree | 9d4bf5f35a18e8d19b0b8bcdcc8258898ac8861f /git-verify-tag.sh | |
parent | format-patch: pretty-print timestamp correctly. (diff) | |
download | tgif-aa064743fa69e2806d5e0af1fab103baa6fa57cd.tar.xz |
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>
Diffstat (limited to 'git-verify-tag.sh')
0 files changed, 0 insertions, 0 deletions