Re: Blaming diffs

Christian Couder [off-list ref] wrote:

Le dimanche 16 septembre 2007, Mike Hommey a écrit :

quoted

It seems to me there is no tool to "blame diffs", i.e. something to know
what commit(s) is(are) responsible for a set of changes.

I don't know if that's what you are looking for but perhaps you could 
use "git bisect run". You just need to pass it a script that returns 1 when 
it finds the changes and 0 otherwise. (See git-bisect man page.)

That's very inefficient to search for something...
 

Sometimes ago I sent a patch that would allow "!" after "git bisect run", 
but it seems to have been forgotten. This patch makes it possible to use:

git bisect run ! grep some_stuff file1 file2...

This would give you the commit where some_stuff was introduced in file1 or 
file2...

Is `git log -Ssome_stuff -- file1 file2` somehow not working for you?

-- 
Shawn.