You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In magit, it's possible to "recursivly blame": In the blame view, move the cursor to a line, then press "b" again to open a blame view of the parent of the revision which modified said line. This allows quickly understanding how a certain feature evolved in a file, and finding older relevant commits and the issue numbers their comments might contain.
Or, as the magit manual states: If Magit-Blame mode is already turned on in the current buffer then blaming is done recursively, by visiting REVISION:FILE (using magit-find-file), where REVISION is a parent of the revision that added the current line or chunk of lines.
I post this because the readme states that feature requests are welcome. Every now and then I miss this feature but not yet enough to submit a PR :)
The text was updated successfully, but these errors were encountered:
In magit, it's possible to "recursivly blame": In the blame view, move the cursor to a line, then press "b" again to open a blame view of the parent of the revision which modified said line. This allows quickly understanding how a certain feature evolved in a file, and finding older relevant commits and the issue numbers their comments might contain.
Or, as the magit manual states: If Magit-Blame mode is already turned on in the current buffer then blaming is done recursively, by visiting REVISION:FILE (using magit-find-file), where REVISION is a parent of the revision that added the current line or chunk of lines.
I post this because the readme states that feature requests are welcome. Every now and then I miss this feature but not yet enough to submit a PR :)
The text was updated successfully, but these errors were encountered: