Hi, Is it just an accident of history or by design that whatchanged requires the -m option to show changes introduced by merges but diff and git log show those changes without requiring any extra options? Would it not make more sense to have git whatchanged show the changes introduced by merges by default and then people can use the (already supported) --no-merges option to suppress that behaviour? It appears that just setting rev.ignore_merges to 0 in cmd_whatchanged() would do the trick. Shall I submit a patch? Mark -- 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
