[PATCH v3 1/4] revisions.txt: change "rev" to "<rev>"
- From
Denton Liu <liu.denton@gmail.com>
- Date
- May 5, 2019, 16:06 UTC
- Message-ID
- <e5b6d69eec80acab5b4b4c702011fc82a7367a79.1557072286.git.liu.denton@gmail.com>
- In-Reply-To
- <cover.1557072286.git.liu.denton@gmail.com>
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 <liu.denton@gmail.com> --- Documentation/revisions.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt index 2337a995ec..e5f11691b1 100644 --- a/Documentation/revisions.txt +++ b/Documentation/revisions.txt @@ -159,12 +159,12 @@ thing no matter the case. '<rev>{caret}0' is a short-hand for '<rev>{caret}\{commit\}'. + -'rev{caret}\{object\}' can be used to make sure 'rev' names an -object that exists, without requiring 'rev' to be a tag, and -without dereferencing 'rev'; because a tag is already an object, +'<rev>{caret}\{object\}' can be used to make sure '<rev>' names an +object that exists, without requiring '<rev>' to be a tag, and +without dereferencing '<rev>'; because a tag is already an object, it does not have to be dereferenced even once to get to an object. + -'rev{caret}\{tag\}' can be used to ensure that 'rev' identifies an +'<rev>{caret}\{tag\}' can be used to ensure that '<rev>' identifies an existing tag object. '<rev>{caret}{}', e.g. 'v0.99.8{caret}{}'::
-- 2.21.0.1049.geb646f7864