From: Junio C Hamano <gitster@pobox.com>
To: "Sokolov\, Konstantin \(ext\)" <konstantin.sokolov.ext@siemens.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Understanding behavior of git blame -M
Date: Fri, 15 Aug 2014 10:07:34 -0700 [thread overview]
Message-ID: <xmqq7g291y21.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <71BF70CE41AEE741896AF3A5450D86F11F28C762@DEFTHW99EH3MSX.ww902.siemens.net> (Konstantin Sokolov's message of "Fri, 15 Aug 2014 13:40:09 +0000")
"Sokolov, Konstantin (ext)" <konstantin.sokolov.ext@siemens.com>
writes:
>>git blame -s -n -f -w -M20 file.txt
> ^2cd9f7f 1 1) AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
> ^2cd9f7f 3 2) CCCCCCCCCCCCCCCCCCCCCCCC2222222222222222222222222
> ^2cd9f7f 4 3) DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD
> d4bbd97e 4 4) BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
> ^2cd9f7f 5 5) EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
> ^2cd9f7f 6 6) GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG
> ^2cd9f7f 7 7) FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
>
> I wonder, why line B is not recognized as moved. According to the
> documentation, I would expect git blame to report that it
> originates from line 2 in revision 2cd9f7f. Can anybody explain
> the behavior?
Interesting. Would it make a difference if you move B further away
from lines A and C?
next prev parent reply other threads:[~2014-08-15 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 13:40 Understanding behavior of git blame -M Sokolov, Konstantin (ext)
2014-08-15 14:42 ` David Kastrup
2014-08-15 20:54 ` AW: " Sokolov, Konstantin (ext)
2014-08-16 7:02 ` David Kastrup
2014-08-16 0:06 ` Duy Nguyen
2014-08-15 17:07 ` Junio C Hamano [this message]
2014-08-15 20:57 ` AW: " Sokolov, Konstantin (ext)
2014-08-18 11:41 ` Sokolov, Konstantin (ext)
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=xmqq7g291y21.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=konstantin.sokolov.ext@siemens.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.