Repository navigation
Remove a flood of maybe irrelevant warnings - #685
Merged
Merged
Conversation
Collaborator
|
@hannesa2 , want me to further investigate this one? |
Contributor
Author
|
If you see space for improvement here, go ahead ! Otherwise I'll merge it, if nothing against it. |
hannesa2
force-pushed
the
RemoveWarnings
branch
from
September 19, 2026 12:11
7cfe542 to
1d10132
Compare
Collaborator
|
The two lines in The bump pins Suggestion: merge the two GitX lines now, and pin the submodule after gitx/objective-git#106 lands on master. |
hannesa2
force-pushed
the
RemoveWarnings
branch
3 times, most recently
from
September 19, 2026 14:12
3400820 to
b7abd22
Compare
hannesa2
force-pushed
the
RemoveWarnings
branch
from
September 19, 2026 14:32
b7abd22 to
3821eed
Compare
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
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.
refs: gitx/objective-git#106
I see a lot of these warnings, and as a non objective-c developer, I try to remove them.
@goneng does this make sense to you ?
There are a lot if remaining warnings (git2.h, git2/annotated_commit.h, etc.) which come from vendored upstream libgit2 itself, which uses quoted includes as normal C-library convention. Rewriting all of libgit2's own headers is out of scope (huge, third-party, would need to be done/maintained upstream).
So I use
CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADERto get rid of them