dunecontrol [IMO] overeagerly checks for version matches
A typical workflow of mine is to type things like this:
dunecontrol exec git checkout releases/2.4 dunecontrol exec git checkout master
This works perfectly fine, if all modules are on compatible branches. However, if they are not, dunecontrol errors out instead of just executing the command.
This would not be very disturbing, if it would not occur in the following scenario: I switch to release branch of all modules until I encounter one that does not have a branch of that name. dunecontrol then errors out and I end up with only half of my modules being switched, resulting in incompatible branches...
In this case, I consider this a bug.