[PATCH v5 09/12] doc: revisions - define `reachable`
From: Philip Oakley <hidden>
Date: 2016-08-12 07:09:12
Subsystem:
documentation, the rest · Maintainers:
Jonathan Corbet, Linus Torvalds
Do not self-define `reachable`, which can lead to misunderstanding. Instead define `reachability` explictly. Signed-off-by: Philip Oakley <redacted> --- unchanged --- Documentation/revisions.txt | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt
index 934d071..238be45 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 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.9.0.windows.1