From: Felipe Contreras Date: Thu, 04 May 2023 16:34:21 GMT Subject: [PATCH 2/2] doc: revisions: add a bunch of missing quotes Message-ID: <20230504163421.100400-3-felipe.contreras@gmail.com> In-Reply-To: <20230504163421.100400-1-felipe.contreras@gmail.com> Signed-off-by: Felipe Contreras --- Documentation/revisions.txt | 36 ++++++++++++++++++------------------ 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt index af764de153..bc1c6e5979 100644 --- a/Documentation/revisions.txt +++ b/Documentation/revisions.txt @@ -97,10 +97,10 @@ some output processing may assume ref names in UTF-8. before the current one. '[]@\{upstream\}', e.g. 'master@\{upstream\}', '@\{u\}':: - A branch B may be set up to build on top of a branch X (configured with - `branch..merge`) at a remote R (configured with - `branch..remote`). B@\{u} refers to the remote-tracking branch for - the branch X taken from remote R, typically found at `refs/remotes/R/X`. + A branch 'B' may be set up to build on top of a branch 'X' (configured with + `branch..merge`) at a remote 'R' (configured with + `branch..remote`). 'B@\{u}' refers to the remote-tracking branch for + the branch 'X' taken from remote 'R', typically found at `refs/remotes/R/X`. '[]@\{push\}', e.g. 'master@\{push\}', '@\{push\}':: The suffix '@\{push}' reports the branch "where we would push to" if @@ -129,7 +129,7 @@ from one location and push to another. In a non-triangular workflow, This suffix is also accepted when spelled in uppercase, and means the same thing no matter the case. -'{caret}[]', e.g. 'HEAD{caret}, v1.5.1{caret}0':: +'{caret}[]', e.g. 'HEAD{caret}', 'v1.5.1{caret}0':: A suffix '{caret}' to a revision parameter means the first parent of that commit object. '{caret}' means the th parent (i.e. '{caret}' @@ -137,7 +137,7 @@ thing no matter the case. '{caret}0' means the commit itself and is used when '' is the object name of a tag object that refers to a commit object. -'{tilde}[]', e.g. 'HEAD{tilde}, master{tilde}3':: +'{tilde}[]', e.g. 'HEAD{tilde}', 'master{tilde}3':: A suffix '{tilde}' to a revision parameter means the first parent of that commit object. A suffix '{tilde}' to a revision parameter means the commit @@ -278,8 +278,8 @@ The '..' (two-dot) Range Notation:: The '{caret}r1 r2' set operation appears so often that there is a shorthand for it. When you have two commits 'r1' and 'r2' (named according to the syntax explained in SPECIFYING REVISIONS above), you can ask - for commits that are reachable from r2 excluding those that are reachable - from r1 by '{caret}r1 r2' and it can be written as 'r1..r2'. + for commits that are reachable from 'r2' excluding those that are reachable + from 'r1' by '{caret}r1 r2' and it can be written as 'r1..r2'. The '\...' (three-dot) Symmetric Difference Notation:: A similar notation 'r1\...r2' is called symmetric difference @@ -288,7 +288,7 @@ The '\...' (three-dot) Symmetric Difference Notation:: It is the set of commits that are reachable from either one of 'r1' (left side) or 'r2' (right side) but not from both. -In these two shorthand notations, you can omit one end and let it default to HEAD. +In these two shorthand notations, you can omit one end and let it default to `HEAD`. For example, 'origin..' is a shorthand for 'origin..HEAD' and asks "What did I do since I forked from the origin branch?" Similarly, '..origin' is a shorthand for 'HEAD..origin' and asks "What did the origin do since @@ -340,22 +340,22 @@ Revision Range Summary ---------------------- '':: - Include commits that are reachable from (i.e. and its + Include commits that are reachable from '' (i.e. '' and its ancestors). '{caret}':: - Exclude commits that are reachable from (i.e. and its + Exclude commits that are reachable from '' (i.e. '' and its ancestors). '..':: - Include commits that are reachable from but exclude - those that are reachable from . When either or - is omitted, it defaults to `HEAD`. + Include commits that are reachable from '' but exclude + those that are reachable from ''. When either '' or + '' is omitted, it defaults to `HEAD`. '\...':: - Include commits that are reachable from either or - but exclude those that are reachable from both. When - either or is omitted, it defaults to `HEAD`. + Include commits that are reachable from either '' or + '' but exclude those that are reachable from both. When + either '' or '' is omitted, it defaults to `HEAD`. '{caret}@', e.g. 'HEAD{caret}@':: A suffix '{caret}' followed by an at sign is the same as listing @@ -367,7 +367,7 @@ Revision Range Summary as giving commit '' and all its parents prefixed with '{caret}' to exclude them (and their ancestors). -'{caret}-', e.g. 'HEAD{caret}-, HEAD{caret}-2':: +'{caret}-', e.g. 'HEAD{caret}-', 'HEAD{caret}-2':: Equivalent to '{caret}..', with '' = 1 if not given. -- 2.40.0+fc1