Documentation: mention config sources for @{upstream}
The earlier documentation made vague references to "is set to build
on". Flesh that out with references to the config settings, so folks
can use git-config(1) to get more detail on what @{upstream} means.
For example, @{upstream} does not care about remote.pushdefault or
branch.<name>.pushremote.
Signed-off-by: W. Trevor King <wking@tremily.us>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
maint
parent
eea591373e
commit
670a7297c2
|
|
@ -94,7 +94,9 @@ some output processing may assume ref names in UTF-8.
|
|||
'<branchname>@\{upstream\}', e.g. 'master@\{upstream\}', '@\{u\}'::
|
||||
The suffix '@\{upstream\}' to a branchname (short form '<branchname>@\{u\}')
|
||||
refers to the branch that the branch specified by branchname is set to build on
|
||||
top of. A missing branchname defaults to the current one.
|
||||
top of (configured with `branch.<name>.remote` and
|
||||
`branch.<name>.merge`). A missing branchname defaults to the
|
||||
current one.
|
||||
|
||||
'<rev>{caret}', e.g. 'HEAD{caret}, v1.5.1{caret}0'::
|
||||
A suffix '{caret}' to a revision parameter means the first parent of
|
||||
|
|
|
|||
Loading…
Reference in New Issue