summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2005-09-18 22:45:09 (GMT)
committerJunio C Hamano <junkio@cox.net>2005-09-18 22:45:09 (GMT)
commit87c6aeb4efdd4355918d127a91bd0adc5a02f8ff (patch)
tree085b53c8c5f017b4d35d0a54304c2885fa5f9a76
parent34143b2639625f29edf7b1c0c5af58e545845911 (diff)
downloadgit-87c6aeb4efdd4355918d127a91bd0adc5a02f8ff.zip
git-87c6aeb4efdd4355918d127a91bd0adc5a02f8ff.tar.gz
git-87c6aeb4efdd4355918d127a91bd0adc5a02f8ff.tar.bz2
Arrgh -- another asciidoc caret workaround.
Signed-off-by: Junio C Hamano <junkio@cox.net>
-rw-r--r--Documentation/git-rev-parse.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt
index 5c136e0..067e4f0 100644
--- a/Documentation/git-rev-parse.txt
+++ b/Documentation/git-rev-parse.txt
@@ -94,7 +94,8 @@ what is called an 'extended SHA1' syntax.
explicitly say 'heads/master' to tell GIT which one you mean.
* A suffix '^' to a revision parameter means the first parent of
- that commit object. '^<n>' means the <n>th parent (i.e. 'rev^'
+ that commit object. '^<n>' means the <n>th parent (i.e.
+ 'rev^'
is equivalent to 'rev^1'). As a special rule,
'rev^0' means the commit itself and is used when 'rev' is the
object name of a tag object that refers to a commit object.