{"thread":{"id":"51089","subject":"git blame doesn't respect diff algorithm?","startedAt":"2019-05-14T09:25:07Z","lastAt":"2019-05-14T09:25:07Z","messageCount":1,"participants":["Pierre Ossman"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"375483","messageId":"f0ed56fd-092e-92e5-35b5-7adfd740d5bf@cendio.se","threadId":"51089","inReplyTo":null,"subject":"git blame doesn't respect diff algorithm?","fromName":"Pierre Ossman","fromEmail":"ossman@cendio.se","sentAt":"2019-05-14T09:19:17Z","receivedAt":"2019-05-14T09:25:07Z","isPatch":false,"sender":{"key":"ossman@cendio.se","avatar":"https://gravatar.com/avatar/d72603ba4ea49f4dd970131b7944709d2c353664d7d389e2264caa6cc8eb618c?d=mp&s=160"},"body":"Hi,\n\nIt seems like there is a bug in git blame where it doesn't respect the\ndiff algorithm setting. It happily parses it on the command line, but\nthere is no change to the output.\n\nThe problem materialises in that git blame will claim a line comes from\na certain commit. But when I do \"git show --patience\" on that commit,\nthe relevant line was not changed.\n\nI could not find anything about this on the mailing list, so is this a\npreviously overlooked issue?\n\nIf you want to test it for your self, then do:\n\n 1. Clone tigervnc's git repo\n 2. git blame --patience vncviewer/DesktopWindow.cxx\n 3. Check line 906, it should say 7e546feba\n 4. git show --patience 7e546feba\n\nThis was with git-2.20.1-1.fc29.x86_64.\n\nRegards\n-- \nPierre Ossman           Software Development\nCendio AB               https://cendio.com\nTeknikringen 8          https://twitter.com/ThinLinc\n583 30 Linköping        https://facebook.com/ThinLinc\nPhone: +46-13-214600\n\nA: Because it messes up the order in which people normally read text.\nQ: Why is top-posting such a bad thing?\n"}]}