undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation: mention push.default in git-push.txt

Browse Source 
It already is listed in the "git config" documentation, but people
interested in pushing would first look at "git push" documentation.

Noticed-by: David Glasser
Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
Acked-by: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Fixed-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Ramkumar Ramachandra 2012-10-02 21:08:00 +05:30 committed by Junio C Hamano
parent d117dd2096
commit 1ec6f488de
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Documentation/git-push.txt
View File

@ -37,7 +37,9 @@ OPTIONS[[OPTIONS]]
`+`, followed by the source ref <src>, followed `+`, followed by the source ref <src>, followed
by a colon `:`, followed by the destination ref <dst>. by a colon `:`, followed by the destination ref <dst>.
It is used to specify with what <src> object the <dst> ref It is used to specify with what <src> object the <dst> ref
in the remote repository is to be updated. in the remote repository is to be updated. If not specified,
the behavior of the command is controlled by the `push.default`
configuration variable.
+ +
The <src> is often the name of the branch you would want to push, but The <src> is often the name of the branch you would want to push, but
it can be any arbitrary "SHA-1 expression", such as `master~4` or it can be any arbitrary "SHA-1 expression", such as `master~4` or
@ -65,7 +67,8 @@ directs git to push "matching" branches: for every branch that exists on
the local side, the remote side is updated if a branch of the same name the local side, the remote side is updated if a branch of the same name
already exists on the remote side. This is the default operation mode already exists on the remote side. This is the default operation mode
if no explicit refspec is found (that is neither on the command line if no explicit refspec is found (that is neither on the command line
nor in any Push line of the corresponding remotes file---see below). nor in any Push line of the corresponding remotes file---see below) and
no `push.default` configuration variable is set.
--all:: --all::
Instead of naming each ref to push, specifies that all Instead of naming each ref to push, specifies that all
@ -357,7 +360,8 @@ Examples
`git push origin :`. `git push origin :`.
+ +
The default behavior of this command when no <refspec> is given can be The default behavior of this command when no <refspec> is given can be
configured by setting the `push` option of the remote. configured by setting the `push` option of the remote, or the `push.default`
configuration variable.
+ +
For example, to default to pushing only the current branch to `origin` For example, to default to pushing only the current branch to `origin`
use `git config remote.origin.push HEAD`. Any valid <refspec> (like use `git config remote.origin.push HEAD`. Any valid <refspec> (like