Jianyu Zhan <nasa4...@gmail.com> writes:
> Usually, a trivial change(like coding style fix) may bury a
> original change of the code, and thus git blame is of less
> help. And to address this situation, I have to do like this:
> git blame -s REF^ <file-in-question> > temp
> to dig into the history recursively by hand, to find out
> the original change.
> Here, REF is commit-id that git blame reports.
> git log -L is a good alternative option, but sometimes it seems
> too cubersome, as I care only one line of code.
> Is there any current solution or suggestion?
git blame -w
might help with a number of "coding style fixes".
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html