diff options
author | Chris Johnsen <chris_johnsen@pobox.com> | 2009-03-14 21:32:01 -0500 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2009-03-17 14:15:04 -0700 |
commit | d6aba61f88dafc10cfb874b91e7864419fa81fd7 (patch) | |
tree | 602a686416713ed077e91e88dd008560b31819a3 /Documentation | |
parent | d42ec126aa717d00549e387d5a95fd55683c2e2c (diff) | |
download | git-d6aba61f88dafc10cfb874b91e7864419fa81fd7.tar.gz git-d6aba61f88dafc10cfb874b91e7864419fa81fd7.tar.xz |
git-push.txt: describe how to default to pushing only current branch
Signed-off-by: Chris Johnsen <chris_johnsen@pobox.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/git-push.txt | 26 |
1 files changed, 24 insertions, 2 deletions
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 4e7e5a719..fd53c49fb 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -24,8 +24,8 @@ every time you push into it, by setting up 'hooks' there. See documentation for linkgit:git-receive-pack[1]. -OPTIONS -------- +OPTIONS[[OPTIONS]] +------------------ <repository>:: The "remote" repository that is destination of a push operation. This parameter can be either a URL @@ -187,6 +187,28 @@ reason:: Examples -------- +git push:: + Works like `git push <remote>`, where <remote> is the + current branch's remote (or `origin`, if no remote is + configured for the current branch). + +git push origin:: + Without additional configuration, works like + `git push origin :`. ++ +The default behavior of this command when no <refspec> is given can be +configured by setting the `push` option of the remote. ++ +For example, to default to pushing only the current branch to `origin` +use `git config remote.origin.push HEAD`. Any valid <refspec> (like +the ones in the examples below) can be configured as the default for +`git push origin`. + +git push origin ::: + Push "matching" branches to `origin`. See + <refspec> in the <<OPTIONS,OPTIONS>> section above for a + description of "matching" branches. + git push origin master:: Find a ref that matches `master` in the source repository (most likely, it would find `refs/heads/master`), and update |