From: Stephen Kitt <steve@sk2.org>
To: git@vger.kernel.org
Cc: gitster@pobox.com, Stephen Kitt <steve@sk2.org>
Subject: [PATCH] docs/git-blame: explain carets on boundary commits
Date: Fri, 8 Jun 2018 21:31:35 +0200 [thread overview]
Message-ID: <20180608193135.31110-1-steve@sk2.org> (raw)
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
reply other threads:[~2018-06-08 19:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180608193135.31110-1-steve@sk2.org \
--to=steve@sk2.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).