Skip to content

Commit 3bae8d4

Browse files
jrngitster
authored andcommitted
Documentation: do not misinterpret pull refspec as bold text
Use the {asterisk} entity to avoid mistreating the asterisks in "(e.g., refs/heads/*:refs/remotes/origin/*)" as delimiters for bold text. From a quick search with 'git grep -e "\*.*\*"', this seems to be the last example of this particular formatting problem. Signed-off-by: Jonathan Nieder <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 7e4eb21 commit 3bae8d4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Documentation/git-pull.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,8 @@ With `--rebase`, it runs 'git rebase' instead of 'git merge'.
2727
passed to linkgit:git-fetch[1]. <refspec> can name an
2828
arbitrary remote ref (for example, the name of a tag) or even
2929
a collection of refs with corresponding remote tracking branches
30-
(e.g., refs/heads/*:refs/remotes/origin/*), but usually it is
31-
the name of a branch in the remote repository.
30+
(e.g., refs/heads/{asterisk}:refs/remotes/origin/{asterisk}),
31+
but usually it is the name of a branch in the remote repository.
3232

3333
Default values for <repository> and <branch> are read from the
3434
"remote" and "merge" configuration for the current branch

0 commit comments

Comments
 (0)