Merged
Conversation
The recent addition of an error code to `pass_whole_blame` in ff8d2eb (blame_git: check return value of object lookup, 2017-03-20) introduced a spurious goto. Remove it.
Member
Author
|
Also added another commit fixing a new memory leak in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The recent addition of an error code to
pass_whole_blamein ff8d2eb(blame_git: check return value of object lookup, 2017-03-20) introduced
a spurious goto. Remove it.
Just noticed a few thousands of new memory leaks in the CI. The error is trivial and kind of embarassing - I'm surprised the compiler didn't throw any warning for unreachable code.