On Mon, May 2, 2022 at 5:18 PM Laurent Pinchart
<laurent.pinchart@xxxxxxxxxxxxxxxx> wrote:
>
> On a side note, navigating removals is something git doesn't make easy:
> git blame will tell when a line has been added (or modified), but
> figuring out when a line has been removed is more difficult. Or is it
> one of git's features that I simply don't know about ?
I find 'git log -p' to almost always be more useful than 'git blame'
when trying to
find out what happened to a file.
What I tend to do is to start with 'git grep $KEYWORD v3.0' (or
2.6.12, 4.0, 5.0 etc)
to see what file mentioned something, and then 'git log -p --
$FILENAME' to see the
commits leading up to the removal.
One bit I find missing though is for 'git log --follow' to track
renames from $FILENAME
to a new location, rather than following where it came from.
Arnd
