Skip to content

Commit e277ff4

Browse files
Denton-Lgitster
authored andcommitted
revisions.txt: change "rev" to "<rev>"
In revisions.txt, there were some instances of a rev argument being written as "rev". However, since they didn't mean the string literal, write "<rev>", instead. Signed-off-by: Denton Liu <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 268fbcd commit e277ff4

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

Documentation/revisions.txt

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -159,12 +159,12 @@ thing no matter the case.
159159
'<rev>{caret}0'
160160
is a short-hand for '<rev>{caret}\{commit\}'.
161161
+
162-
'rev{caret}\{object\}' can be used to make sure 'rev' names an
163-
object that exists, without requiring 'rev' to be a tag, and
164-
without dereferencing 'rev'; because a tag is already an object,
162+
'<rev>{caret}\{object\}' can be used to make sure '<rev>' names an
163+
object that exists, without requiring '<rev>' to be a tag, and
164+
without dereferencing '<rev>'; because a tag is already an object,
165165
it does not have to be dereferenced even once to get to an object.
166166
+
167-
'rev{caret}\{tag\}' can be used to ensure that 'rev' identifies an
167+
'<rev>{caret}\{tag\}' can be used to ensure that '<rev>' identifies an
168168
existing tag object.
169169

170170
'<rev>{caret}{}', e.g. 'v0.99.8{caret}{}'::

0 commit comments

Comments
 (0)