Le dimanche 16 septembre 2007, Mike Hommey a écrit : > Hi, > > 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.) 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... Regards, Christian. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
