You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Find out which commit corresponds to the last release
Browse files of the repo for that commit
CTRL+F for seL4 in the Readme
Copy paste the matching seL4 commit id
Paste that into my buildscript.
From an information standpoint, mentioning the seL4 commit id in the README has a similar effect like having the git submodule file with the repo URL and commit id, just its less formal/harder to parse by tools
If the correct seL4 repo would be a submodule, my workflow could become:
Recursively checkout the current release version of this repo
The text was updated successfully, but these errors were encountered:
My current workflow for tracking microkit is:
From an information standpoint, mentioning the seL4 commit id in the README has a similar effect like having the git submodule file with the repo URL and commit id, just its less formal/harder to parse by tools
If the correct seL4 repo would be a submodule, my workflow could become:
The text was updated successfully, but these errors were encountered: