Making Changes to a Component Code (lammps,latte or parsplice)
All changes to the component codes of EXAALT (lammps,latte or par splice) should be performed within their respective repositories, stored in ~/exaalt_dev/exaalt_comps/.
For example, making a change to LATTE to address a specific issue (issue iss17 in this example):
cd ~/exaalt_dev/exaalt_comps/latte/ git checkout -b iss17 master touch newfile.c git add newfile.c git commit -m "Adding new file (new file.c) to latte" git push -u origin iss17
When you are happy with your changes and are ready to merge with the master branch, you can submit a merge request:
git checkout master git merge iss17
Differences in LAMMPS and ParSplice
Note that, because the exaalt/lammps repository is mirroring the LAMMPS github repository, development will not take place on the master branch, but on the exaalt branch. Therefore, the example above will change to:
cd ~/exaalt_dev/exaalt_comps/lammps/ git checkout -b iss17 exaalt touch newfile.c git add newfile.c git commit -m "Adding new file (new file.c) to lammps" git push -u origin iss17 git checkout exaalt git merge iss17
For ParSplice, the master branch could be used without any complications of mirroring. However, this repository will also treat the exaalt branch as the mater branch for consistency (and to avoid merge request delays).