New answers tagged magit
1
Wow, it's almost too easy. Just go to the other commit in the log buffer, show it, and use "a" to apply each change to the current working dir.
2
The activity you are describing is commonly called "blaming". Magit's manual contains a section about blaming.
The easiest way to show such information is to type C-c M-g b in a file-visiting buffer, but there are alternative approaches as described in the manual.
0
(Disclaimer: I don't know if this is how Magit and Spacemacs actually work, but it fits my hypothesis.)
When you magit-checkout a remote branch, magit can't know if the current file you have open in the buffer also exists in the remote branch. However, git-checkout changed the file, so a workaround (pointed out in a comment by MTS) is to revert the file (...
2
That was a bug and I have fixed it.
I suggest you delete your question because it is no longer relevant. Then again not everyone updates when encountering an issue.
0
You can use the hook git-commit-finish-query-functions to implement arbitrary restrictions.
2
When viewing a merge commit or while hovering it in the log, press d r <RET> to open a diff view showing all the changes.
Top 50 recent answers are included
