Merge master to dev16.0 #5143
Merged
Merge master to dev16.0 #5143
Conversation
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
* normalize source and create line endings array both used for format string parsing once per file * comments * let lazy do its job * remove parens
Contributor
|
@brettfo Am I correct in thinking we should use "create a merge commit" rather than "squash and merge" for these? |
Member
|
Yes, "create a merge commit" is correct to properly preserve history. |
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.
This is an automatically generated pull request from master into dev16.0.
git fetch --all git checkout merges/master-to-dev16.0 git reset --hard upstream/dev16.0 git merge upstream/master # Fix merge conflicts git commit git push merges/master-to-dev16.0 --forceOnce all conflicts are resolved and all the tests pass, you are free to merge the pull request.