-
-
Notifications
You must be signed in to change notification settings - Fork 799
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parens stripped from log messages #3
Comments
Test show that this seem to be solved. Could you confirm it ? |
Works for me in at least 862f364 |
this issue is stil present. But for it to show up, you need to have no ref/* point to the commit in question. |
pjweisberg
added a commit
that referenced
this issue
May 17, 2011
When attempting to delete a remote-tracking branch and the associated remote branch with `k` in the branch manager, the code prior to this change would: 1) Delete the branch at point. 2) Refresh the buffer as a side effect of calling Git. 3) Delete the remote branch referred to by the branch at point. Of course, the branch at point in #3 is NOT the same branch that was at point when the user pressed `k`. I introduced this bug when I taught the branch manager's buffer how to respond to magit-refresh. To fix it, I capture the branch information in a variable before making any changes, and use that variable instead of any *-at-point functions. I also don't change anything until after asking the user if he wants to remove the remote branch as well, so the selected branch is still visible when the question is asked.
kenny-thomas
pushed a commit
to kenny-thomas/magit
that referenced
this issue
Aug 22, 2017
Turn off save-place in git-commit mode, if available
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
`l' gave me this line for one commit:
7a4d10dd * cosmetic Use Path for cleanliness
the actual commit comment is “(cosmetic) Use Path for cleanliness”
The text was updated successfully, but these errors were encountered: