Browse Source

doc: revisions - clarify reachability examples

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 <philipoakley@iee.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
maint
Philip Oakley 9 years ago committed by Junio C Hamano
parent
commit
1afe13b98a
  1. 11
      Documentation/revisions.txt

11
Documentation/revisions.txt

@ -253,7 +253,8 @@ Commit Exclusions @@ -253,7 +253,8 @@ Commit Exclusions
'{caret}<rev>' (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 the ones reachable from 'r1' (i.e. 'r1' and
its ancestors).

Dotted Range Notations
~~~~~~~~~~~~~~~~~~~~~~
@ -297,12 +298,12 @@ Revision Range Summary @@ -297,12 +298,12 @@ Revision Range Summary
----------------------

'<rev>'::
Include commits that are reachable from (i.e. ancestors of)
<rev>.
Include commits that are reachable from <rev> (i.e. <rev> and its
ancestors).

'{caret}<rev>'::
Exclude commits that are reachable from (i.e. ancestors of)
<rev>.
Exclude commits that are reachable from <rev> (i.e. <rev> and its
ancestors).

'<rev1>..<rev2>'::
Include commits that are reachable from <rev2> but exclude

Loading…
Cancel
Save