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>
Philip Oakley committed
Aug 12, 2016 at 08:07 UTC
0b451248b398240c92bc2d48e96d7c3838c12349
1 file changed
+10
-4
Documentation/revisions.txt
+10
-4
@@ -236,10 +236,16 @@ SPECIFYING RANGES
236
-----------------
237
238
History traversing commands such as `git log` operate on a set
239
-of commits, not just a single commit. To these commands,
240
-specifying a single revision with the notation described in the
241
-previous section means the set of commits reachable from that
242
-commit, following the commit ancestry chain.
239
+of commits, not just a single commit.
240
+
241
+For these commands,
242
+specifying a single revision, using the notation described in the
243
+previous section, means the set of commits `reachable` from the given
244
+commit.
245
+
246
+A commit's reachable set is the commit itself and the commits in
247
+its ancestry chain.
248
+
249
250
Commit Exclusions
251
~~~~~~~~~~~~~~~~~