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>
Philip Oakley committed
Aug 12, 2016 at 08:07 UTC
1afe13b98a9865c012daffca5d0ac56aced318fb
1 file changed
+6
-5
Documentation/revisions.txt
+6
-5
@@ -253,7 +253,8 @@ Commit Exclusions
253
'{caret}<rev>' (caret) Notation::
254
To exclude commits reachable from a commit, a prefix '{caret}'
255
notation is used. E.g. '{caret}r1 r2' means commits reachable
256
- from 'r2' but exclude the ones reachable from 'r1'.
256
+ from 'r2' but exclude the ones reachable from 'r1' (i.e. 'r1' and
257
+ its ancestors).
258
259
Dotted Range Notations
260
~~~~~~~~~~~~~~~~~~~~~~
@@ -297,12 +298,12 @@ Revision Range Summary
298
----------------------
299
300
'<rev>'::
300
- Include commits that are reachable from (i.e. ancestors of)
301
- <rev>.
301
+ Include commits that are reachable from <rev> (i.e. <rev> and its
302
+ ancestors).
303
304
'{caret}<rev>'::
304
- Exclude commits that are reachable from (i.e. ancestors of)
305
- <rev>.
305
+ Exclude commits that are reachable from <rev> (i.e. <rev> and its
306
+ ancestors).
307
308
'<rev1>..<rev2>'::
309
Include commits that are reachable from <rev2> but exclude