Documentation update for spack stack create env --upstream
#714
Conversation
This file contains 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
…pack stack create env' extension
ulmononian
approved these changes
Aug 16, 2023
climbfuji
deleted the
feature/doc_update_spack_stack_create_env_upstream
branch
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.
Summary
This PR updates and cleans up the documentation for the newly added
spack stack create env --upstreamfunctionality. The spack submodule pointer update is for the changes in JCSDA/spack#303.Testing
Tested locally on my macOS.
Applications affected
n/a
Systems affected
Potentially all due to minor bug fixes in JCSDA/spack#303
Dependencies
Issue(s) addressed
Addresses #690 (comment)
Checklist