Re: [Ksummit-discuss] checkkpatch (in)sanity ?

From: Joe Perches <joe@perches.com>
Date: Aug 28, 2016, 21:57 UTC
Message-ID: <1472421462.26978.134.camel@perches.com>
In-Reply-To: <1472419498.4265.16.camel@kaarsemaker.net>

On Sun, 2016-08-28 at 23:24 +0200, Dennis Kaarsemaker wrote:

Show 11 quoted lines

> > 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?
> tig has a neat way of doing blame history digging: do a `tig blame
> filename`, select a line and hit the comma key to re-blame from the
> parent of the commit that was blamed for that line.

Thanks, of course I neglected to mention tig.

What I think some here want is the ability to view back and forth from old to new rather than just split the window horizontally with the commit content.

Basically, apply the patch hunks for a specific range to see color coded changes rather just show the entire patch in a separate view.

Sure, seeing the commit log and patch is useful.

Seeing the block of code pre and post patch for the specific section can be more useful.