The previous subtree add should not have been landed onto the runtime/ prefix, which confuses subtree split because of that subdirectory being referenced in previous commits (before we performed the subtree add). This produces commit histories with two initial commits (one from sedwards-lab/ssm and one from Rewbert/ssm-edsl). This makes pushing out of this repo rather difficult and unpleasant.
This PR redoes subtree add but with a unique prefix (lib/ssm), while deleting the old runtime/ directory---from this repo's perspective, this is effectively performing a git mv. A lot of the commits from my zephyr-work branch are also included here, but are reverted in later commits (a lot of the runtime examples work will be moved to a different repo where I won't be polluting a git history).
The previous
subtree addshould not have been landed onto theruntime/prefix, which confusessubtree splitbecause of that subdirectory being referenced in previous commits (before we performed the subtree add). This produces commit histories with two initial commits (one from sedwards-lab/ssm and one from Rewbert/ssm-edsl). This makes pushing out of this repo rather difficult and unpleasant.This PR redoes
subtree addbut with a unique prefix (lib/ssm), while deleting the oldruntime/directory---from this repo's perspective, this is effectively performing agit mv. A lot of the commits from myzephyr-workbranch are also included here, but are reverted in later commits (a lot of the runtime examples work will be moved to a different repo where I won't be polluting a git history).