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. The rest of the documentation uses backticks
whenever a caret is encountered in running text, so do the same here.
Signed-off-by: brian m. carlson sand...@crustytoothpaste.net
---
Documentation/git-rev-parse.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt
index 9bd76a5..074030f 100644
--- 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 `^{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`
--
2.0.1
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
