Code style overhaul#1878
Closed
bagder wants to merge 6 commits into
Closed
Conversation
... as the code style mandates.
bagder
force-pushed
the
bagder/checksrc-equals-checks
branch
from
35d0568 to
e393459
Compare
Contributor
|
Not very friendly to people who backport patches to |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
I made
checksrcwarn for lines of code that use=or+without sufficient spacing next to them. I then changed all code to adhere to this.Or code style guidelines already says we should write code that way, and most of the code does.
This is the next step in making our code style more uniform.