RE: Understanding behavior of git blame -M

Seems like not detecting single line movements is per design and just the documentation is not precise about this. Could such an enhancement be considered as a feature request? We're using git (blame) as a low level tool for building further functionality on top of it. Maintaining a custom

Re: AW: Understanding behavior of git blame -M

Sokolov, Konstantin (ext) konstantin.sokolov@siemens.com writes: Hi David, thank you very much for the exhaustive answer. The keyword hunk made me try a little bit more. So I realized that -M works as expected when at least three lines are moved. From your answer I discern that you

Understanding behavior of git blame -M

Hi Folks, I'm trying to understand the behavior of git blame -M and find that the actual results differ from what I understood from the documentation. I've already asked longer time ago on stackoverflow and on the user mailing list without any satisfactory results. So here is the example:

Re: Understanding behavior of git blame -M

Sokolov, Konstantin (ext) konstantin.sokolov@siemens.com writes: Hi Folks, I'm trying to understand the behavior of git blame -M and find that the actual results differ from what I understood from the documentation. I've already asked longer time ago on stackoverflow and on the user

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) A ^2cd9f7f 3 2) 2 ^2cd9f7f 4 3)

AW: Understanding behavior of git blame -M

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: Hi Folks, I'm trying to understand the behavior of git blame -M and find that the actual results differ from what I understood

AW: Understanding behavior of git blame -M

: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) A ^2cd9f7f 3 2

Re: Understanding behavior of git blame -M

On Fri, Aug 15, 2014 at 9:42 PM, David Kastrup d...@gnu.org wrote: The function diff_hunks is a wrapper for the diff engine. Putting the context length explicitly into this wrapper (rather than not passing an argument and just setting the context length to zero anyway in the function) clearly