On Sun, 2016-08-28 at 11:59 +0200, Julia Lawall wrote: > On Sun, 28 Aug 2016, Alexey Dobriyan wrote: [] > > The problem is that c-h.pl generates noise in the commit history and > > makes git-blame less useful than it can be. > > Could it be that this is a problem with git blame, rather than with > checkpatch? Last year there was a discussion on this list about how there > is an option to git blame that will cause it to step through the history, > and not show only the most recent patch that has modified a given line. It is more or less an ease-of-use limitation of git blame. There are some that want an ncurses only version of git blame that could use arrow-key style navigation for historical commit line-ranges. git gui blame kind of works, but it's not ncurses/text based. git-cola kind of works too, but it's not text based either. Are there other existing tools for blame history viewing? -- 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