# Is there something like a blamed diff? 4 messages from 2014-02-15 to 2014-02-17. Participants: David Kastrup, Thomas Rast. Thread: https://gitlist.dev/t/35885 ## David Kastrup, 2014-02-15 18:38 Subject: Is there something like a blamed diff? Message-ID: <8738jk1as7.fsf@fencepost.gnu.org> URL: https://gitlist.dev/e/8738jk1as7.fsf%40fencepost.gnu.org ``` When comparing two branches, decorating the flat diff with the respectively responsible commits seems like it would be nice to do/have (the blame on the identical parts, in contrast, is not really interesting). Is there any tool that provides something like that? -- David Kastrup ``` ## Thomas Rast, 2014-02-17 10:24 Subject: Re: Is there something like a blamed diff? Message-ID: <87ioseujej.fsf@thomasrast.ch> URL: https://gitlist.dev/e/87ioseujej.fsf%40thomasrast.ch In-Reply-To: <8738jk1as7.fsf@fencepost.gnu.org> ``` David Kastrup writes: > When comparing two branches, decorating the flat diff with the > respectively responsible commits seems like it would be nice to do/have > (the blame on the identical parts, in contrast, is not really > interesting). Is there any tool that provides something like that? This seems to come up every year or so: http://thread.gmane.org/gmane.comp.version-control.git/110369/focus=110383 -- Thomas Rast tr@thomasrast.ch ``` ## David Kastrup, 2014-02-17 11:02 Subject: Re: Is there something like a blamed diff? Message-ID: <8761oeuhmg.fsf@fencepost.gnu.org> URL: https://gitlist.dev/e/8761oeuhmg.fsf%40fencepost.gnu.org In-Reply-To: <87ioseujej.fsf@thomasrast.ch> ``` Thomas Rast writes: > David Kastrup writes: > >> When comparing two branches, decorating the flat diff with the >> respectively responsible commits seems like it would be nice to do/have >> (the blame on the identical parts, in contrast, is not really >> interesting). Is there any tool that provides something like that? > > This seems to come up every year or so: > > http://thread.gmane.org/gmane.comp.version-control.git/110369/focus=110383 Nice. That one could likely be sped up by calling git-blame just once on each file with multiple -L options. Though actually with the current implementation of git-blame you are likely faster for a large number of differences by doing each region separately anyway since then the cost for digging through the history is obviously O(n) for n consecutive runs on n chunks while the administrative overhead for several chunks in a single run is O(n^2) at the moment. -- David Kastrup ``` ## Thomas Rast, 2014-02-17 17:41 Subject: Re: Is there something like a blamed diff? Message-ID: <87ppmltz5y.fsf@thomasrast.ch> URL: https://gitlist.dev/e/87ppmltz5y.fsf%40thomasrast.ch In-Reply-To: <8761oeuhmg.fsf@fencepost.gnu.org> ``` David Kastrup writes: > Thomas Rast writes: > >> David Kastrup writes: >> >>> When comparing two branches, decorating the flat diff with the >>> respectively responsible commits seems like it would be nice to do/have >>> (the blame on the identical parts, in contrast, is not really >>> interesting). Is there any tool that provides something like that? >> >> This seems to come up every year or so: >> >> http://thread.gmane.org/gmane.comp.version-control.git/110369/focus=110383 > > Nice. That one could likely be sped up by calling git-blame just once > on each file with multiple -L options. Yes. You'll note that the email predates the support for multiple -L options by a few years :-) I never had a need for such a script, I just wrote that in response to someone asking about it. If you find it useful, please clean it up for inclusion in contrib/. -- Thomas Rast tr@thomasrast.ch ```