AW: git blame swallows up lines in case of mixed line endings

#x27;s possible in general (by changing the implementation)? Kind Regards Konstantin -Ursprüngliche Nachricht- Von: Junio C Hamano [mailto:gits...@pobox.com] Gesendet: Montag, 23. Februar 2015 19:45 An: Torsten Bögershausen Cc: Sokolov, Konstantin (ext); 'git@vger.kernel.org

AW: git blame swallows up lines in case of mixed line endings

e) we run into consistency problems. -Ursprüngliche Nachricht- Von: Torsten Bögershausen [mailto:tbo...@web.de] Gesendet: Samstag, 21. Februar 2015 14:46 An: Sokolov, Konstantin (ext); 'git@vger.kernel.org' Betreff: Re: git blame swallows up lines in case of mixed line endings

git blame swallows up lines in case of mixed line endings

Hi Folks, I encounter unexpected behavior in the following case: file content: line1 line2 line3 line4 This is what I get as console output (on Windows): > git blame -s file.txt 7db36436 1) line1 line3436 2) line2 7db36436 3) line4 This is the real content: > git blame -s file.txt > blame.tx

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 versi

AW: Understanding behavior of git blame -M

14 19:08 An: Sokolov, Konstantin (ext) Cc: git@vger.kernel.org Betreff: Re: Understanding behavior of git blame -M "Sokolov, Konstantin (ext)" writes: >>git blame -s -n -f -w -M20 file.txt > ^2cd9f7f 1 1)

AW: Understanding behavior of git blame -M

gnu.org] Gesendet: Freitag, 15. August 2014 16:42 An: Sokolov, Konstantin (ext) Cc: git@vger.kernel.org Betreff: Re: Understanding behavior of git blame -M "Sokolov, Konstantin (ext)" writes: > Hi Folks, > > I'm trying to understand the behavior of git blame -M and

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: Init

git blame -M seems not to work as expected

Hi Folks! I've posed this question already on stackoverflow and on Google Groups - without any (satisfying) answer. So maybe you can help me to understand the behavior of git blame -M. First I commit the following file(file.cpp): void func1(){return;}[CR][LF] int func2(){return 23;}[CR][LF]