Don't merge Feature/v4.0.4 to master #5
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
Feature/fix merge on 4.0.4
Feature/pathfix
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.
Working tutorial for NEMO 4.0.4 for Singularity container and on ARCHER2.
Demonstration for tide only or tide plus weather.
This NEMO version is in between the old svn system and the new git system, so it was easier to dump the entire source code here rather than to figure out the edits to a no longer maintained version control repo. Consequently the history of this version is quite a jump from the last version, on svn. And the next version (on git) will be big a big departure from this. So I am thinking to manage the release and any update on branch
feature/v4.0.4, rather than push to master.