{"thread":{"id":"35885","subject":"Is there something like a blamed diff?","startedAt":"2014-02-15T18:38:32Z","lastAt":"2014-02-17T17:41:13Z","messageCount":4,"participants":["David Kastrup","Thomas Rast"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"234862","messageId":"8738jk1as7.fsf@fencepost.gnu.org","threadId":"35885","inReplyTo":null,"subject":"Is there something like a blamed diff?","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2014-02-15T18:38:32Z","receivedAt":"2014-02-15T18:38:32Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"\nWhen comparing two branches, decorating the flat diff with the\nrespectively responsible commits seems like it would be nice to do/have\n(the blame on the identical parts, in contrast, is not really\ninteresting).  Is there any tool that provides something like that?\n\n-- \nDavid Kastrup\n"},{"id":"234916","messageId":"87ioseujej.fsf@thomasrast.ch","threadId":"35885","inReplyTo":"8738jk1as7.fsf@fencepost.gnu.org","subject":"Re: Is there something like a blamed diff?","fromName":"Thomas Rast","fromEmail":"tr@thomasrast.ch","sentAt":"2014-02-17T10:24:04Z","receivedAt":"2014-02-17T10:24:04Z","isPatch":false,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"David Kastrup <dak@gnu.org> writes:\n\n> When comparing two branches, decorating the flat diff with the\n> respectively responsible commits seems like it would be nice to do/have\n> (the blame on the identical parts, in contrast, is not really\n> interesting).  Is there any tool that provides something like that?\n\nThis seems to come up every year or so:\n\nhttp://thread.gmane.org/gmane.comp.version-control.git/110369/focus=110383\n\n-- \nThomas Rast\ntr@thomasrast.ch\n"},{"id":"234917","messageId":"8761oeuhmg.fsf@fencepost.gnu.org","threadId":"35885","inReplyTo":"87ioseujej.fsf@thomasrast.ch","subject":"Re: Is there something like a blamed diff?","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2014-02-17T11:02:31Z","receivedAt":"2014-02-17T11:02:31Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"Thomas Rast <tr@thomasrast.ch> writes:\n\n> David Kastrup <dak@gnu.org> writes:\n>\n>> When comparing two branches, decorating the flat diff with the\n>> respectively responsible commits seems like it would be nice to do/have\n>> (the blame on the identical parts, in contrast, is not really\n>> interesting).  Is there any tool that provides something like that?\n>\n> This seems to come up every year or so:\n>\n> http://thread.gmane.org/gmane.comp.version-control.git/110369/focus=110383\n\nNice.  That one could likely be sped up by calling git-blame just once\non each file with multiple -L options.\n\nThough actually with the current implementation of git-blame you are\nlikely faster for a large number of differences by doing each region\nseparately anyway since then the cost for digging through the history is\nobviously O(n) for n consecutive runs on n chunks while the\nadministrative overhead for several chunks in a single run is O(n^2) at\nthe moment.\n\n-- \nDavid Kastrup\n"},{"id":"234930","messageId":"87ppmltz5y.fsf@thomasrast.ch","threadId":"35885","inReplyTo":"8761oeuhmg.fsf@fencepost.gnu.org","subject":"Re: Is there something like a blamed diff?","fromName":"Thomas Rast","fromEmail":"tr@thomasrast.ch","sentAt":"2014-02-17T17:41:13Z","receivedAt":"2014-02-17T17:41:13Z","isPatch":false,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"David Kastrup <dak@gnu.org> writes:\n\n> Thomas Rast <tr@thomasrast.ch> writes:\n>\n>> David Kastrup <dak@gnu.org> writes:\n>>\n>>> When comparing two branches, decorating the flat diff with the\n>>> respectively responsible commits seems like it would be nice to do/have\n>>> (the blame on the identical parts, in contrast, is not really\n>>> interesting).  Is there any tool that provides something like that?\n>>\n>> This seems to come up every year or so:\n>>\n>> http://thread.gmane.org/gmane.comp.version-control.git/110369/focus=110383\n>\n> Nice.  That one could likely be sped up by calling git-blame just once\n> on each file with multiple -L options.\n\nYes.  You'll note that the email predates the support for multiple -L\noptions by a few years :-)\n\nI never had a need for such a script, I just wrote that in response to\nsomeone asking about it.  If you find it useful, please clean it up for\ninclusion in contrib/.\n\n-- \nThomas Rast\ntr@thomasrast.ch\n"}]}