If you look at the output from the "kernel/printk.c" with this patch, you would notice that there still are somewhat meaningless merges shown in the history (e.g. scroll down to 185a257f2f73bcd89050ad02da5bedbc28fc43fa). The mainline side keeps making steady changes to the path, but the side branch that made tty_write_message available to others with b346671 ([PATCH] Export tty_write_message() for GFS2 quota code, 2006-01-16) keeps many "Merge from master" until it is merged back to the mainline, even after the earlier change is reverted by 02630a1 ([GFS2] Remove dependance on tty_write_message(), 2006-07-03). I wonder if we can do something clever to reduce these pointless (from the point of view of explaining kernel/printk.c's evolution, at least) merges from the output. This might be another example of the reason why it is a good thing that you keep teaching people: "On your xyzzy topic, you are doing xyzzy development, not xyzzy development plus random changes --- don't merge my tree into yours!", and we could dismiss these extra merges we see in the output as artifacts from a bad practice, but as long as we are spending extra cycles, it would be better if we could reduce such clutter. I am still undecided about the option name. The existing --full-history is "show history fully without simplifying the merge at all". This is "show history fully with merge simplification". Perhaps --simplify-merges? -- 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
