Closed gagachang closed 1 year ago
Hello,
It is expected. The manifest file in the master branch points to the latest optee_*
code (it has revision="master"
). When a new release is tagged, the manifest is modified to make the subprojects point to that tag instead (revision="refs/tags/4.0.0"
), so it is one commit ahead (the commit that changes "master"
to "refs/tags/4.0.0"
). The master branch is left untouched because we still want it to track master.
Oh! I didn't realize it. Thanks for explanation.
Hello It seems that
master
branch hasn't been synchronized to version 4.0.0