doc: improve formatting in branch section

The 'branch' section of the git-config documentation was missing
inline code formatting and emphasis for the <name> placeholder.

Both changes improve readability, especially when viewed online.

Signed-off-by: Jakub Ječmínek <kuba@kubajecminek.cz>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
maint
Jakub Ječmínek 2025-06-29 21:04:45 +02:00 committed by Junio C Hamano
parent 16bd9f20a4
commit 996f14c02b
1 changed files with 2 additions and 2 deletions

View File

@ -69,9 +69,9 @@ This option defaults to `never`.
`git fetch`) to lookup the default branch for merging. Without
this option, `git pull` defaults to merge the first refspec fetched.
Specify multiple values to get an octopus merge.
If you wish to setup `git pull` so that it merges into <name> from
If you wish to setup `git pull` so that it merges into _<name>_ from
another branch in the local repository, you can point
branch.<name>.merge to the desired branch, and use the relative path
`branch.<name>.merge` to the desired branch, and use the relative path
setting `.` (a period) for `branch.<name>.remote`.

`branch.<name>.mergeOptions`::