summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLibravatar Philip Oakley <philipoakley@iee.org>2016-08-12 08:07:46 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-08-13 19:36:44 -0700
commit0b451248b398240c92bc2d48e96d7c3838c12349 (patch)
tree3c9c1b66894e9dbe7489ce0418b2b01bb51b948f
parentdoc: gitrevisions - clarify 'latter case' is revision walk (diff)
downloadtgif-0b451248b398240c92bc2d48e96d7c3838c12349.tar.xz
doc: revisions - define `reachable`
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>
-rw-r--r--Documentation/revisions.txt14
1 files 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
~~~~~~~~~~~~~~~~~