[PATCH] docs/git-blame: explain carets on boundary commits

From: Stephen Kitt <steve@sk2.org>
Date: Jun 8, 2018, 19:31 UTC
Message-ID: <20180608193135.31110-1-steve@sk2.org>

The caret on boundary commits is only mentioned in the description of --abbrev; this patch adds a description of the behaviour in the paragraph describing how revision range specifiers are handled.

Signed-off-by: Stephen Kitt <steve@sk2.org>
---
 Documentation/git-blame.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt
index 16323eb80..7f814dcef 100644
--- a/Documentation/git-blame.txt
+++ b/Documentation/git-blame.txt
@@ -163,7 +163,8 @@ When revision range specifiers are used to limit the annotation,
 lines that have not changed since the range boundary (either the
 commit v2.6.18 or the most recent commit that is more than 3
 weeks old in the above example) are blamed for that range
-boundary commit.
+boundary commit.  The sha1 is preceded by a caret, '^' to indicate
+this (and its length is reduced by 1).
 
 A particularly useful way is to see if an added file has lines
 created by copy-and-paste from existing files.  Sometimes this

-- 
2.11.0