summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorDenton Liu <liu.denton@gmail.com>2019-05-05 16:07:07 (GMT)
committerJunio C Hamano <gitster@pobox.com>2019-05-07 15:09:06 (GMT)
commit6a12e99a52d2d01ea84e5040a87e0dac0a4b0b35 (patch)
treee69399b5f67ce52497b28971bba6fb146c2ac6e2 /Documentation
parentd86d207471e3411ceb2969f1066e31fb4ca144dc (diff)
downloadgit-6a12e99a52d2d01ea84e5040a87e0dac0a4b0b35.zip
git-6a12e99a52d2d01ea84e5040a87e0dac0a4b0b35.tar.gz
git-6a12e99a52d2d01ea84e5040a87e0dac0a4b0b35.tar.bz2
revisions.txt: mention <rev>~ form
In revisions.txt, the '<rev>^' form is mentioned but the '<rev>~' form is missing. Although both forms are essentially equivalent (they each get the first parent of the specified revision), we should mention the latter for completeness. Make this change. Signed-off-by: Denton Liu <liu.denton@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/revisions.txt4
1 files changed, 3 insertions, 1 deletions
diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt
index 6f2f83f..b5d9d1b 100644
--- a/Documentation/revisions.txt
+++ b/Documentation/revisions.txt
@@ -139,7 +139,9 @@ thing no matter the case.
'<rev>{caret}0' means the commit itself and is used when '<rev>' is the
object name of a tag object that refers to a commit object.
-'<rev>{tilde}<n>', e.g. 'master{tilde}3'::
+'<rev>{tilde}[<n>]', e.g. 'HEAD{tilde}, master{tilde}3'::
+ A suffix '{tilde}' to a revision parameter means the first parent of
+ that commit object.
A suffix '{tilde}<n>' to a revision parameter means the commit
object that is the <n>th generation ancestor of the named
commit object, following only the first parents. I.e. '<rev>{tilde}3' is