From: ryenus Date: Wed, 16 Aug 2017 03:21:10 GMT Subject: [PATCH] fix revisions doc about quoting for ':/' notation Message-ID: To make sure the `` in `:/` is seen as one search string, one should quote/escape `` properly. Especially, the example given in the manual `:/fix nasty bug` does not work because of missing quotes. The examples are now corrected, and a note about quoting/escaping is added as well. --- Documentation/revisions.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt index 61277469c..fdfdde0ad 100644 --- a/Documentation/revisions.txt +++ b/Documentation/revisions.txt @@ -169,14 +169,14 @@ existing tag object. and dereference the tag recursively until a non-tag object is found. -'{caret}{/}', e.g. 'HEAD^{/fix nasty bug}':: +'{caret}{/}', e.g. 'HEAD^{/"fix nasty bug"}':: A suffix '{caret}' to a revision parameter, followed by a brace pair that contains a text led by a slash, is the same as the ':/fix nasty bug' syntax below except that it returns the youngest matching commit which is reachable from the '' before '{caret}'. -':/', e.g. ':/fix nasty bug':: +':/', e.g. ':/"fix nasty bug"':: A colon, followed by a slash, followed by a text, names a commit whose commit message matches the specified regular expression. This name returns the youngest matching commit which is @@ -185,7 +185,8 @@ existing tag object. e.g. ':/^foo'. The special sequence ':/!' is reserved for modifiers to what is matched. ':/!-foo' performs a negative match, while ':/!!foo' matches a literal '!' character, followed by 'foo'. Any other sequence beginning with - ':/!' is reserved for now. + ':/!' is reserved for now. And make sure to quote/escape for the text to be + seen as one search string. ':', e.g. 'HEAD:README', ':README', 'master:./README':: A suffix ':' followed by a path names the blob or tree -- 2.14.1