No. The distance seems to have no influence. In the meantime I've found out (as mentioned in my other reply) that the movements are detected if at least three lines are moved.
-----Ursprüngliche Nachricht----- Von: Junio C Hamano [mailto:gits...@pobox.com] Gesendet: Freitag, 15. August 2014 19:08 An: Sokolov, Konstantin (ext) Cc: git@vger.kernel.org Betreff: Re: Understanding behavior of git blame -M "Sokolov, Konstantin (ext)" <konstantin.sokolov....@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? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
