Skip to content
/ git Public
forked from git/git

Commit

Permalink
doc: revisions - clarify reachability examples
Browse files Browse the repository at this point in the history
 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>
  • Loading branch information
Philip Oakley authored and gitster committed Jul 20, 2016
1 parent 59e0b20 commit 4418733
Showing 1 changed file with 6 additions and 5 deletions.
11 changes: 6 additions & 5 deletions Documentation/revisions.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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
~~~~~~~~~~~~~~~~~~~~~~
Expand Down Expand Up @@ -292,12 +293,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
Expand Down

0 comments on commit 4418733

Please sign in to comment.