remote.*.push is considered before push.default, but there's no mention about that, except a bit in the examples. The description of push.default does say something about this, but it would be easier to find out if it's described here.
The first paragraph describing refspec format is moved down, so that the new first paragraph is about unspsecified refspec and the remaining paragraphs refspec format. Signed-off-by: Nguyễn Thái Ngọc Duy <pclo...@gmail.com> --- Documentation/git-push.txt | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 1398025..20bf2f5 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -33,13 +33,16 @@ OPTIONS[[OPTIONS]] of a remote (see the section <<REMOTES,REMOTES>> below). <refspec>...:: - The format of a <refspec> parameter is an optional plus - `+`, followed by the source ref <src>, followed - by a colon `:`, followed by the destination ref <dst>. - It is used to specify with what <src> object the <dst> ref - in the remote repository is to be updated. If not specified, - the behavior of the command is controlled by the `push.default` - configuration variable. + Specify how how refs are pushed. If not specified and + configuration variable `remote.<remote>.push` is set, the + variable is used as default refspec. If not specified and the + variable is not set, the behavior of the command is controlled + by the `push.default` configuration variable. ++ +The format of a <refspec> parameter is an optional plus `+`, followed +by the source ref <src>, followed by a colon `:`, followed by the +destination ref <dst>. It is used to specify with what <src> object +the <dst> ref in the remote repository is to be updated. + 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 -- 18.104.22.168.536.gf441e6d -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html