build_source_code.md: Update from Spack v0.22 to Spack v1.1#1154
Draft
harshula wants to merge 1 commit intodevelopmentfrom
Draft
build_source_code.md: Update from Spack v0.22 to Spack v1.1#1154harshula wants to merge 1 commit intodevelopmentfrom
harshula wants to merge 1 commit intodevelopmentfrom
Conversation
|
harshula
force-pushed
the
update-to-spack-v1.1
branch
from
39ce7c3 to
1ccfaca
Compare
Contributor
Author
|
Hi @atteggiani , Since all the development work is now focussed on ESM1.6, should we update this document to use ACCESS-ESM1.6 as the example instead of ACCESS-ESM1.5? |
Contributor
Yes, I think it makes sense as it will be more relevant for readers. |
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
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.
This PR shouldn't be merged till ACCESS-ESM1.5 migrates to Spack v1.1 via PR ACCESS-NRI/ACCESS-ESM1.5#46 .