Find git commits related to a certain part of a file

Quite often I find myself staring at some old code that doesn’t look right. It looks like something has been removed (e.g. it has a loop that does nothing of value, or it creates a variable but doesn’t use it), or something is just hard to understand the point of. In these cases I would really need to see the history of that section of the file. Not all of the file though, just that section, or function.

Ideal solution
A simple command like

  • How to create a repository with ssh:// access on a server
  • Git: merge only the changes made on the branch
  • How does Git handle branches compared to SVN?
  • Double commits in git history after `git format-patch`,`git am`, `git pull`
  • Why can two git worktrees not check out the same branch?
  • git: updates were rejected because the remote contains work that you do not have locally
  • git log books.cpp:10

    to find history of line 10 (possibly with surroundings) of file books.cpp is probably too much magic to ask for, but do you have ideas of how to work out that history?

    What I have tried
    I have tried using blame, and then checking out the commit before the given commit of that line – repeating it until I’ve seen enough. But that is very tedious work.

    Have you felt the need for this feature? Do you have a way of achieving it? Share your experience!

  • How does my git repository keep getting corrupted?
  • Git asking for password.
  • Creating a hidden directory in a repository
  • Git & development setup for solo developer
  • Git diffing crashes on Windows when submodules exist
  • `git clone` over HTTP Fails with “repository not found”
  • 2 Solutions collect form web for “Find git commits related to a certain part of a file”

    Git is very easy to extend. Does something like this achieve what you want?

    for hash in `git log --pretty=format:%h ${FILENAME}`
        echo "***************** Showing ${FILENAME} at ${hash}"
        git blame -L ${LINENUMBERS} ${hash} ${FILENAME}

    Put this little script in your path as something like git-linehistory and call it like this:

    git linehistory books.cpp 5,15

    It will show you what lines 5 to 15 look like at each commit for that file.

    • git blame -L option lets you specify a range of line to output, or even a regexp to match the function you want.
    • You can also specify to blame at a specific commit, then you don’t have to checkout the revision before the blame.

    So in short you can do successive calls to git blame -L range <commit> <file-name> to browse the history of line by line changes.

    Git Baby is a git and github fan, let's start git clone.