doc: fix unquoted use of "{type}"

peff · gitster · commit b50bfb8fd535 · 2015-05-12T22:13:40.000-07:00
Curly braces open an "attribute" in AsciiDoc; if there's no
such attribute, strange things may happen. In this case, the
unquoted "{type}" causes AsciiDoc to omit an entire line of
text from the output. We can fix it by putting the whole
phrase inside literal backticks (which also lets us get rid
of ugly backslash escaping).

Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt
@@ -102,7 +102,7 @@ eval "set -- $(git rev-parse --sq --prefix "$prefix" "$@")"
 +
 If you want to make sure that the output actually names an object in
 your object database and/or can be used as a specific type of object
-you require, you can add "\^{type}" peeling operator to the parameter.
+you require, you can add the `^{type}` peeling operator to the parameter.
 For example, `git rev-parse "$VAR^{commit}"` will make sure `$VAR`
 names an existing object that is a commit-ish (i.e. a commit, or an
 annotated tag that points at a commit).  To make sure that `$VAR`

Original file line number	Diff line number	Diff line change
`@@ -102,7 +102,7 @@ eval "set -- $(git rev-parse --sq --prefix "$prefix" "$@")"`
`102`	`102`	`+`
`103`	`103`	`If you want to make sure that the output actually names an object in`
`104`	`104`	`your object database and/or can be used as a specific type of object`
`105`		`-you require, you can add "\^{type}" peeling operator to the parameter.`
	`105`	+you require, you can add the `^{type}` peeling operator to the parameter.
`106`	`106`	For example, `git rev-parse "$VAR^{commit}"` will make sure `$VAR`
`107`	`107`	`names an existing object that is a commit-ish (i.e. a commit, or an`
`108`	`108`	annotated tag that points at a commit). To make sure that `$VAR`