{"push_id":823367855,"size":1,"distinct_size":1,"ref":"refs/heads/devel","head":"c6e129a05862742e949e1c6cc41d65ce3e044268","before":"6129c3adfcecd98ac6f09e0545520e8d160dabc7","commits":[{"sha":"c6e129a05862742e949e1c6cc41d65ce3e044268","author":{"email":"fec605d29867ebfb61868c05cfc08af32675474e@posteo.net","name":"deso"},"message":"introduce git-blamediff script\n\nWhen working with git it is often a necessity to know which change set a\ngiven line was changed in in order to merge something in or amend it in\nsome other way. In general, this task can be accomplished by git's\n'blame' or 'annotate' commands.\nIt gets more interesting when one wants to annotate exactly what is in a\npatch. That is, one wants to retrieve such an annotation for exactly\nthose lines present in a diff in order to generate fix up commits, for\ninstance.\nThis change introduces the git-blamediff script which can be used to\nsimplify this task. The script reads from standard input (where it\nexpects a diff), extracts the different hunks, and invokes git blame for\neach of them. A sample invocation could look like this:\n  $ git diff | git blamediff\n\nIn its current state, the annotation is always performed against HEAD\nwhich makes sense in general for invocations of git 'diff' but not for\nother commands such as 'show'.\n\nNote: In order for git's 'blame' command to be able to directly\n      understand the paths supplied you have to produce the diffs\n      without a prefix. That is, the --no-prefix option should be passed\n      to git's 'diff' command.\n      Furthermore, in order for the script to work properly from\n      directories other than the root of the git repository you will\n      need to produce diffs with relative paths, i.e., pass in the\n      --relative option as well.","distinct":true,"url":"https://api.github.com/repos/d-e-s-o/git-blamediff/commits/c6e129a05862742e949e1c6cc41d65ce3e044268"}]}