From 0b451248b398240c92bc2d48e96d7c3838c12349 Mon Sep 17 00:00:00 2001 From: Philip Oakley Date: Fri, 12 Aug 2016 08:07:46 +0100 Subject: [PATCH] doc: revisions - define `reachable` Do not self-define `reachable`, which can lead to misunderstanding. Instead define `reachability` explictly. Signed-off-by: Philip Oakley Signed-off-by: Junio C Hamano --- Documentation/revisions.txt | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt index f3a53a662b..f223a1cc40 100644 --- a/Documentation/revisions.txt +++ b/Documentation/revisions.txt @@ -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 ~~~~~~~~~~~~~~~~~ -- 2.11.4.GIT