Specify branches in all rosinstall files

[matthiashh]

This is one of the things, I wonder that I didn't run into earlier.

I just noticed that if one checks out a branch through a rosinstall file, e.g.

- git: {local-name: libs/skiros2/skiros2, uri: '[email protected]:robotlab/rvmi/skiros2.git', version: 'develop'}

and then use another rosinstall file that doesn't specify a branch

- git: {local-name: libs/skiros2/skiros2, uri: '[email protected]:robotlab/rvmi/skiros2.git'}

it doesn't revert back to master, but stay in the previous branch and just checks if the repo exists.
I will specify master branches now, you could consider doing the same.

[matthiashh]

Of course this comes at the cost that every time you update your checked out branches are overwritten.
But the update script doesn't switch branches in rvmi_workspace_setup before applying a rosinstall file, so one could just make a branch here that has a rosinstall file with the correct branches one is working on.