From: Philip Oakley Date: Mon, 11 Jul 2016 20:25:18 GMT Subject: [PATCH v3 8/8] doc: revisions - clarify reachability examples Message-ID: <20160711202518.532-9-philipoakley@iee.org> In-Reply-To: <20160711202518.532-1-philipoakley@iee.org> For the r1..r2 case, the exclusion of r1, rather than inclusion of r2, would be the unexpected case in natural language for a simple linear development, i.e. start..end excludes start. Signed-off-by: Philip Oakley --- Documentation/revisions.txt | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt index a3cd28b..dba4fc6 100644 --- a/Documentation/revisions.txt +++ b/Documentation/revisions.txt @@ -252,7 +252,8 @@ The '{caret}' (caret) notation ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To exclude commits reachable from a commit, a prefix '{caret}' notation is used. E.g. '{caret}r1 r2' means commits reachable -from 'r2' but exclude the ones reachable from 'r1'. +from 'r2' but exclude those reachable from 'r1' (i.e. 'r1' and its +ancestors). The '..' (two-dot) range notation ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -290,12 +291,12 @@ Revision Range Summary ---------------------- '':: - Include commits that are reachable from (i.e. ancestors of) - . + Include commits that are reachable from (i.e. and its + ancestors). '{caret}':: - Exclude commits that are reachable from (i.e. ancestors of) - . + Exclude commits that are reachable from (i.e. and its + ancestors). '..':: Include commits that are reachable from but exclude -- 2.8.4.windows.1.3.ge328a54