Documentation: fix missing text for rev-parse --verify

bk2204 · gitster · commit e6aaa393478b · 2014-07-22T10:10:57.000-07:00
The caret (^) is used as a markup symbol in AsciiDoc.  Due to the
inability of AsciiDoc to parse a line containing an unmatched caret, it
omitted the line from the output, resulting in the man page missing the
end of a sentence.  Escape this caret so that the man page ends up with
the complete text.

Signed-off-by: brian m. carlson &lt;sandals@crustytoothpaste.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
@@ -98,7 +98,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 "\^{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
`@@ -98,7 +98,7 @@ eval "set -- $(git rev-parse --sq --prefix "$prefix" "$@")"`
`98`	`98`	`+`
`99`	`99`	`If you want to make sure that the output actually names an object in`
`100`	`100`	`your object database and/or can be used as a specific type of object`
`101`		`-you require, you can add "^{type}" peeling operator to the parameter.`
	`101`	`+you require, you can add "\^{type}" peeling operator to the parameter.`
`102`	`102`	For example, `git rev-parse "$VAR^{commit}"` will make sure `$VAR`
`103`	`103`	`names an existing object that is a commit-ish (i.e. a commit, or an`
`104`	`104`	annotated tag that points at a commit). To make sure that `$VAR`