Sanjiv Gupta <sanjiv.gupta@xxxxxxxxxxxxx> writes: > I was looking for post-mortem change-that-introduced-bug. If so, then you don't need to test every commit. As David mentionned, "git bisect" is your friend, and will do a binary search, finding the culprit commit much more efficiently (run the testsuite log(n) times instead of n times). OTOH, if you want some kind of quality insurance (i.e. check that every commit is OK, including the case where a commit introduces a bug, and the next one fixes it), bisect is rather helpless. -- Matthieu -- 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