Skip to content

Commit fef0e99

Browse files
jherlandgitster
authored andcommitted
Refer to branch.<name>.remote/merge when documenting --track
Make it easier for readers to find the actual config variables that implement the "upstream" relationship. Suggested-by: Per Cederqvist <[email protected]> Signed-off-by: Johan Herland <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 81f339d commit fef0e99

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

Documentation/git-branch.txt

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,8 @@ working tree to it; use "git checkout <newbranch>" to switch to the
4848
new branch.
4949

5050
When a local branch is started off a remote-tracking branch, Git sets up the
51-
branch so that 'git pull' will appropriately merge from
51+
branch (specifically the `branch.<name>.remote` and `branch.<name>.merge`
52+
configuration entries) so that 'git pull' will appropriately merge from
5253
the remote-tracking branch. This behavior may be changed via the global
5354
`branch.autosetupmerge` configuration flag. That setting can be
5455
overridden by using the `--track` and `--no-track` options, and
@@ -156,7 +157,8 @@ This option is only applicable in non-verbose mode.
156157

157158
-t::
158159
--track::
159-
When creating a new branch, set up configuration to mark the
160+
When creating a new branch, set up `branch.<name>.remote` and
161+
`branch.<name>.merge` configuration entries to mark the
160162
start-point branch as "upstream" from the new branch. This
161163
configuration will tell git to show the relationship between the
162164
two branches in `git status` and `git branch -v`. Furthermore,

0 commit comments

Comments
 (0)