Going one step further from git blame --reverse ?

Hi,

Once again I've found myself in the annoying position to find out why a particular line that was present in an older version was removed (i.e. I needed to find the first commit it is not present in).

git blame --reverse brings me close, but not quite there, and quite often it will point at a commit where several branches diverged.

Is there a way to make it go one step further and report the commit whose message is most likely to explain things?

    Simon