You can specify a revision for git blame to look back starting from (instead of the default of HEAD); fe25b6d^ is the parent of fe25b6d.
Edit: New to Git 2.23, we have the --ignore-rev option added to git blame:
git blame --ignore-rev fe25b6d
While this doesn't answer OP's question of giving the stack of commits (you'll use git log for that, as per the other answer), it is a better way of this solution, as you won't potentially misblame the other lines.
Gives you a nice graphical display of changes like "git blame" but with clickable links per line, to move into earlier commits. Hover over the links to get a popup with commit details. Not my credits... found it here:
git gui is a graphical Tcl/Tc interface to git. Without any other params it starts a pretty simple but useful graphical app for committing files, hunks or even single lines and other similar commands like amend, revert, push... It's part of the git stock suite. On windows it is included in the installer. On debian - I don't know about other *nix systems - it has to be installed separately:
A Tcl/Tk based graphical user interface to Git. git gui focuses on
allowing users to make changes to their repository by making new
commits, amending existing ones, creating branches, performing local
merges, and fetching/pushing to remote repositories.
Unlike gitk, git gui focuses on commit generation and single file
annotation and does not show project history. It does however supply
menu actions to start a gitk session from within git gui.
git gui is known to work on all popular UNIX systems, Mac OS X, and
Windows (under both Cygwin and MSYS). To the extent possible OS
specific user interface guidelines are followed, making git gui a
fairly native interface for users.
Start a blame viewer on the specified file on the given version (or working directory if not specified).
Start a tree browser showing all files in the specified commit. Files selected through the browser are opened in the blame viewer.
Start git gui and arrange to make exactly one commit before exiting and returning to the shell. The interface is limited to only
commit actions, slightly reducing the application’s startup time and
simplifying the menubar.
If you are using JetBrains Idea IDE (and derivatives) you can select several lines, right click for the context menu, then Git -> Show history for selection. You will see list of commits which were affecting the selected lines:
Building on the previous answer, this bash one-liner should give you what you're looking for. It displays the git blame history for a particular line of a particular file, through the last 5 revisions:
LINE=10 FILE=src/options.cpp REVS=5; for commit in $(git rev-list -n $REVS HEAD $FILE); do git blame -n -L$LINE,+1 $commit -- $FILE; done
In the output of this command, you might see the content of the line change, or the line number displayed might even change, for a particular commit.
This often indicates that the line was added for the first time, after that particular commit. It could also indicate the line was moved from another part of the file.