From: Denton Liu <liu.denton@gmail.com>
Date: Sun, 5 May 2019 16:07:07 +0000 (-0400)
Subject: revisions.txt: mention <rev>~ form
X-Git-Tag: v2.22.0-rc0~6^2~1
X-Git-Url: https://git.lorimer.id.au/gitweb.git/diff_plain/6a12e99a52d2d01ea84e5040a87e0dac0a4b0b35

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>
---

diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt
index 6f2f83f8a2..b5d9d1b381 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