Re: Improve `git log -L` functionality

On Sat, Mar 10 2018, KES jotted: > uh... seems nobody is interested in this functionality ( I'm interested in this, and would review a patch to implement this. Generally speaking when you send a "wouldn't it be neat if..." message to the Git mailing list a lot of people read it (including

Re: Improve `git log -L` functionality

uh... seems nobody is interested in this functionality ( 06.03.2018, 17:46, "KES" : > Hi. >  I want to `Trace the evolution of the line range`. > And not committed change is sort of evolution and should be taken into > account by -L option. > > Currently I MUST `stash save`

Improve `git log -L` functionality

Hi. I want to `Trace the evolution of the line range`. And not committed change is sort of evolution and should be taken into account by -L option. Currently I MUST `stash save` change, look actual line number, trace evolution, `stash pop` to bring back current change. EXPECTED: Allow to