{"thread":{"id":"16729","subject":"[BUG] The description of pickaxe in git-blame(1) is wrong","startedAt":"2008-12-14T21:33:48Z","lastAt":"2008-12-14T21:33:48Z","messageCount":1,"participants":["Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"97893","messageId":"200812142233.49669.jnareb@gmail.com","threadId":"16729","inReplyTo":null,"subject":"[BUG] The description of pickaxe in git-blame(1) is wrong","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2008-12-14T21:33:48Z","receivedAt":"2008-12-14T21:33:48Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"I think that the description of how 'pickaxe' feature works in\nDocumentation/git-blame.txt is wrong. It says:\n\n  Apart from supporting file annotation, git also supports searching the\n  development history for when a code snippet occurred in a change. This makes it\n  possible to track when a code snippet was added to a file, moved or copied\n  between files, and eventually deleted or replaced. _It works by searching for\n  a text string in the diff_. A small example:\n\nThe part \"It works by searching for a text string in the diff\" is,\nif I remember correctly, wrong. Actually it (I think) compares how\nmany matches are in pre-image and in post-image, and shows these\ncommits where those number differ.\n\nThis for example means that pickaxe would not pick commit which\nmoved a fragment from one place to other without change, I think.\n\n-- \nJakub Narebski\nPoland\n"}]}