-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port to GNU Fortran on Windows and/or Linux. #17
base: master
Are you sure you want to change the base?
Conversation
Corrections: 1. Replace few remaining author names by 'OPS-Support'. 2. Remove trailing spaces on each line. 3. Remove unused end-of-line comments (multiple spaces followed by line end).
# Conflicts: # m_ops_emis.f90 # ops_main.f90 # ops_read_ctr.f90
This reverts commit 4b8dfa7. It concerns functional bugs, non-porting.
# Conflicts: # m_getkey.f90 # m_ops_building.f90 # m_ops_emis.f90 # ops_main.f90 # ops_read_ctr.f90
# Conflicts: # m_getkey.f90
Ter info, wellicht al bekend: Jeroen Laros heeft ca. een jaar geleden al aanpassingen gedaan om de code goed te laten compileren onder Linux met GNU tools. Ook heeft hij een Makefile erbij geleverd. Hij had dit voor het RIVM gedaan. Het lijkt erop dat zijn aanpassingen niet doorgevoerd zijn de main branch. |
Relatie leggen naar deels functioneel vergelijkbare change nav opmerking @evert-mouw: #1 |
@evert-mouw Ik denk dat we nu wel allemaal kunnen concluderen dat OpenSource en RIVM niet samen gaat. |
Dat bewust weglaten van een Makefile was wel echt ... nouja. We houden hoop ;-) PS: ik zit bepaald niet in de buurt, maar we spreken nog wel een keer IRL |
First of all, we'd like to apologise for the late reaction. We'll try to reply more quickly to future issues and pull requests. Thank you for this pull request. The development of OPS takes place on an internal RIVM Gitlab server. Therefore, this pull request cannot be merged directly into this repository. However, useful suggestions will be implemented in future OPS versions. In the following months, we will try to process each pull request manually and we will update this pull request once it has been processed. For future suggestions for code changes, please contact us by creating an issue or via [email protected] before submitting a pull request. |
Changes developed by Gerard Cats.