@antis81, this change is right; but not exactly what i was thinking about: the call to `MacGitver::repoMan().activate(x)` should be complete by itself. Meaning that in `RepoInfoModel`, you should make your `invalidate()` a slot and connect it to RepoManager's `repositoryActivated` singal.

Also note, that on every such change, 2 Items must be updated. Thus, you need to teach `RepoManager` to also send a signal on de-activation of a repository and connect that to the model's `invalidate()` slot, too. Btw. I would rename it to `invalidateRepository`.

The whole reasoning behind this is, that repositories can also be activated/deactivated by other code paths - not just user interaction via ctx menu of RepoTree.
Actually, _this_ is the kind of event-system that we will sooner or later have to create (or better expand with things like: "headChanged()" etc)...