From: Philip Oakley Date: Mon, 11 Jul 2016 20:25:17 GMT Subject: [PATCH v3 7/8] doc: revisions - define `reachable` Message-ID: <20160711202518.532-8-philipoakley@iee.org> In-Reply-To: <20160711202518.532-1-philipoakley@iee.org> Do not self-define `reachable`, which can lead to misunderstanding. Instead define `reachability` explictly. Signed-off-by: Philip Oakley --- Documentation/revisions.txt | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt index 1c59e87..a3cd28b 100644 --- a/Documentation/revisions.txt +++ b/Documentation/revisions.txt @@ -237,10 +237,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 `reachable` set of commits of the given +commit. + +A commit's reachable set is the commit itself and the commits of +its ancestry chain. + The '{caret}' (caret) notation ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- 2.8.4.windows.1.3.ge328a54