News
[ATTENTION]: Upstream Changes and Git Submodule Repos
Written on 01.11.2024 23:20 by Tejas Harith
Hi all,
Thank you for getting started early on the project assignment and helping me iron out some rough edges! I have made a couple changes to the README where the `make check` vs `make tests` rules were inconsistent with what existed in the Makefile or `sudo` was missing from the chroot command. Please pull the upstream changes from the class main project repo. Some of the changes will fix a broken PERF output for `printf` test.
There was one important factor I overlooked which was committing changes inside the submodule. It is essential that you have your own submodule that you can organise and add branches to, so I have created new submodule repos for you all who registered for the "Project Git Repo" and you should have received an email for it.
Since some of you may have already gotten started, instead of forcibly changing the submodule pointer for you, I have given instructions in the forum. Please see the forum response here. Please ask any follow up questions there. Pointing to your submodule and committing changes there will be necessary for the project milestone 1. Although your private submodules should already have all the necessary files for milestone 1, you should point to the public main submodule repo with
git remote add upstream https://gitlab.cs.uni-saarland.de/os/swish-24ws/project-vortex-swish.git
after which you can use
git fetch upstream ms1
git merge upstream/ms1
to sync up with new milestones to the submodule.
Ultimately the gitlab ci/cd will still use your main project repo's `msX-submission` branch so make sure that the submodule is pointing to your `vortex-swish` repo and the correct commit/branch!
Thanks for bearing with the bugs and I appreciate you all for bringing them to my attention!
Tejas