From: Richard Hansen Date: Mon, 02 Sep 2013 05:34:25 GMT Subject: [PATCH v2 6/7] revisions.txt: fix and clarify ^{} Message-ID: <1378100066-31889-7-git-send-email-rhansen@bbn.com> In-Reply-To: <1378100066-31889-1-git-send-email-rhansen@bbn.com> If possible, will be dereferenced even if it is not a tag type (e.g., commit dereferenced to a tree). Signed-off-by: Richard Hansen --- Documentation/revisions.txt | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt index 569b563..1f1e79b 100644 --- a/Documentation/revisions.txt +++ b/Documentation/revisions.txt @@ -111,10 +111,14 @@ some output processing may assume ref names in UTF-8. '{caret}\{\}', e.g. 'v0.99.8{caret}\{commit\}':: A suffix '{caret}' followed by an object type name enclosed in - brace pair means the object - could be a tag, and dereference the tag recursively until an - object of that type is found or the object cannot be - dereferenced anymore (in which case, barf). '{caret}0' + brace pair means dereference the object at '' recursively until + an object of type '' is found or the object cannot be + dereferenced anymore (in which case, barf). + For example, if '' is a committish, '{caret}\{commit\}' + describes the corresponding commit object. + Similarly, if '' is a treeish, '{caret}\{tree\}' describes + the corresponding tree object. + '{caret}0' is a short-hand for '{caret}\{commit\}'. + 'rev{caret}\{object\}' can be used to make sure 'rev' names an -- 1.8.4