summaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorCarl Worth <cworth@cworth.org>2006-02-22 04:28:50 (GMT)
committerJunio C Hamano <junkio@cox.net>2006-02-22 06:11:50 (GMT)
commitaa064743fa69e2806d5e0af1fab103baa6fa57cd (patch)
tree9d4bf5f35a18e8d19b0b8bcdcc8258898ac8861f /t
parentfab5de7936f0cc086836a38d2de4374c3df223b4 (diff)
downloadgit-aa064743fa69e2806d5e0af1fab103baa6fa57cd.zip
git-aa064743fa69e2806d5e0af1fab103baa6fa57cd.tar.gz
git-aa064743fa69e2806d5e0af1fab103baa6fa57cd.tar.bz2
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 't')
0 files changed, 0 insertions, 0 deletions