RE: Understanding behavior of git blame -M

2014-08-18 Thread Sokolov, Konstantin (ext)
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 versi

Re: Understanding behavior of git blame -M

2014-08-15 Thread Duy Nguyen
On Fri, Aug 15, 2014 at 9:42 PM, David Kastrup 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 indicate

Re: Understanding behavior of git blame -M

2014-08-15 Thread Junio C Hamano
"Sokolov, Konstantin (ext)" writes: >>git blame -s -n -f -w -M20 file.txt > ^2cd9f7f 1 1) A > ^2cd9f7f 3 2) 2 > ^2cd9f7f 4 3) D > d4bbd97e 4 4) B

Re: Understanding behavior of git blame -M

2014-08-15 Thread David Kastrup
"Sokolov, Konstantin (ext)" 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 mailing list without any satis