v4.1.x: README: update --enable-heterogeneous warning #9810
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
Somehow the "do not use the heterogeneous!" warning ended up in the wrong section (as evidenced by open-mpi#9697 (comment)). Move it to the correct section, and also make it crystal clear that the warning is about the heterogeneous functionality. Signed-off-by: Jeff Squyres <[email protected]>
This was referenced Feb 4, 2022
bwbarrett
approved these changes
Feb 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Somehow the "do not use the heterogeneous!" warning ended up in the
wrong section (as evidenced by
#9697 (comment)).
Move it to the correct section, and also make it crystal clear that
the warning is about the heterogeneous functionality.
Signed-off-by: Jeff Squyres [email protected]
bot:notacherrypick
This is not a cherry pick because the warning is in the correct location on master's README.md -- somehow it ended up being in the incorrect location here on the v4.0.x/v4.1.x branches. 🤷♂️