Make the boundary commits' ^ caret findable in the documentation. Signed-off-by: Philip Oakley <philipoakley@iee.email> --- Documentation/git-blame.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt index 7e81541996..02f9ad6fe9 100644 --- a/Documentation/git-blame.txt +++ b/Documentation/git-blame.txt @@ -87,8 +87,8 @@ include::blame-options.txt[] --abbrev=<n>:: Instead of using the default 7+1 hexadecimal digits as the - abbreviated object name, use <n>+1 digits. Note that 1 column - is used for a caret to mark the boundary commit. + abbreviated commit object name, use <n>+1 digits. Note that 1 column + is used for a caret (`^`) to mark boundary commits. THE PORCELAIN FORMAT @@ -164,7 +164,7 @@ 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 (preceded by `^` if shown). A particularly useful way is to see if an added file has lines created by copy-and-paste from existing files. Sometimes this -- 2.26.2.windows.1.13.g9dddff6983
