Torsten Tejlmand Rasmussen

> > Comparing to `git`, this is also why, users must install git-hooks themselves, and you cannot force a git-hook onto another persons machine. > > I agree. This should...

> This would only happen on the very first west update and then again only if the post update scripts are changed after an update. except people who switch between...

Why not a simple: `west config update.projects -- +projectA,+projectB` and if those are set, then a clean `west update` will only update those particular project, just a if `west update...

This is intended to facilitate downstream work, where several developers may share a branch. I suggest adding additional setting to the schema for the project map, so that one may...

Something else to consider. `west.yml` has changed (e.g. after a `git checkout` in manifest repo), and is now specifying a project where the branch shall be checked out by `west`...

some users might prefer to specify remotes where branches to be checked out, so that if `west.yml` points elsewhere, then `west` uses default behavior. so maybe consider the alternative: ```...

> Trying to treat the manifest repository as an ordinary Project was doomed to failure what kind of issues are observed with the current behavior. Could you try to list...

> Welcome back :). Thanks, hope I can still keep a little up to date on `west` ;-) > The manifest repository is a repository for sure, and its Python...

> > leading to errors, which is also a bad sign. > > For example, `west forall -h` _still_ says that the projects list defaults to "all projects in the...

:warning: In case you start doing some work on this, remember that Zephyr modules uses `west list` to obtain a list of ALL projects, as those are candidates for being...