doc: revisions - define `reachable`
authorPhilip Oakley <philipoakley@iee.org>
Fri, 12 Aug 2016 07:07:46 +0000 (08:07 +0100)
committerJunio C Hamano <gitster@pobox.com>
Sun, 14 Aug 2016 02:36:44 +0000 (19:36 -0700)
Do not self-define `reachable`, which can lead to misunderstanding.
Instead define `reachability` explictly.

Signed-off-by: Philip Oakley <philipoakley@iee.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/revisions.txt
index f3a53a662b0dc3bbedc868774f56c3dc2a3140e4..f223a1cc4009e9f44239b24b3a3f9aefd955ab14 100644 (file)
@@ -236,10 +236,16 @@ SPECIFYING RANGES
 -----------------
 
 History traversing commands such as `git log` operate on a set
-of commits, not just a single commit.  To these commands,
-specifying a single revision with the notation described in the
-previous section means the set of commits reachable from that
-commit, following the commit ancestry chain.
+of commits, not just a single commit.
+
+For these commands,
+specifying a single revision, using the notation described in the
+previous section, means the set of commits `reachable` from the given
+commit.
+
+A commit's reachable set is the commit itself and the commits in
+its ancestry chain.
+
 
 Commit Exclusions
 ~~~~~~~~~~~~~~~~~