[PATCH] Documentation: do not misinterpret pull refspec as bold text

[PATCH] Documentation: do not misinterpret pull refspec as bold text

[Jonathan Nieder]

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 <jrnieder@gmail.com>
---
Noticed while reading the pull --rebase documentation[1] suggestions.
[1] http://thread.gmane.org/gmane.comp.version-control.git/162837

 Documentation/git-pull.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt
index e47361f..a421789 100644
--- a/Documentation/git-pull.txt
+++ b/Documentation/git-pull.txt
@@ -27,8 +27,8 @@ With `--rebase`, it runs 'git rebase' instead of 'git merge'.
 passed to linkgit:git-fetch[1].  <refspec> can name an
 arbitrary remote ref (for example, the name of a tag) or even
 a collection of refs with corresponding remote-tracking branches
-(e.g., refs/heads/*:refs/remotes/origin/*), but usually it is
-the name of a branch in the remote repository.
+(e.g., `refs/heads/{asterisk}:refs/remotes/origin/{asterisk}`),
+but usually it is the name of a branch in the remote repository.
 
 Default values for <repository> and <branch> are read from the
 "remote" and "merge" configuration for the current branch
-- 
1.7.2.4

Re: [PATCH] Documentation: do not misinterpret pull refspec as bold text

[Junio C Hamano]

Thanks.