Skip to content

Commit 6a12e99

Browse files
Denton-Lgitster
authored andcommitted
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 <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent d86d207 commit 6a12e99

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

Documentation/revisions.txt

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,9 @@ thing no matter the case.
139139
'<rev>{caret}0' means the commit itself and is used when '<rev>' is the
140140
object name of a tag object that refers to a commit object.
141141

142-
'<rev>{tilde}<n>', e.g. 'master{tilde}3'::
142+
'<rev>{tilde}[<n>]', e.g. 'HEAD{tilde}, master{tilde}3'::
143+
A suffix '{tilde}' to a revision parameter means the first parent of
144+
that commit object.
143145
A suffix '{tilde}<n>' to a revision parameter means the commit
144146
object that is the <n>th generation ancestor of the named
145147
commit object, following only the first parents. I.e. '<rev>{tilde}3' is

0 commit comments

Comments
 (0)