Uh oh!
There was an error while loading. Please reload this page.
Include libgit2 headers in a more consistent manner. - #336
Merged
Conversation
QuLogic
commented
Mar 31, 2018
Contributor
- Move them before git2r headers (few files needed this, but it made them more consistent with the rest),
- Use angle-brackets to differentiate public headers from libgit2 (making it easier to see where stuff might break due to depending on libgit2's internal API),
- and remove some extraneous includes.
Move them before git2r headers, use angle-brackets to differentiate public headers, and remove some extraneous includes. Signed-off-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
coveralls
commented
Mar 31, 2018
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.