Skip to content

Commit 996f14c

Browse files
kubajecminekgitster
authored andcommitted
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 <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 16bd9f2 commit 996f14c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Documentation/config/branch.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -69,9 +69,9 @@ This option defaults to `never`.
6969
`git fetch`) to lookup the default branch for merging. Without
7070
this option, `git pull` defaults to merge the first refspec fetched.
7171
Specify multiple values to get an octopus merge.
72-
If you wish to setup `git pull` so that it merges into <name> from
72+
If you wish to setup `git pull` so that it merges into _<name>_ from
7373
another branch in the local repository, you can point
74-
branch.<name>.merge to the desired branch, and use the relative path
74+
`branch.<name>.merge` to the desired branch, and use the relative path
7575
setting `.` (a period) for `branch.<name>.remote`.
7676
7777
`branch.<name>.mergeOptions`::

0 commit comments

Comments
 (0)