Interestingly only shows in particular python versions
on travis.
Maybe some caching effect?

Locally it is reproducible easily, with the latest flake8

When the code is run without setting up loggers, the loggers have no
handlers for the emitted messages. The logging module displays:
`No handlers could be found for logger "git.cmd"` on the
console. By adding a NullHandler (a no-op) the message disappears,
and doesn't affect logging when other handlers are configured.

Previously we could try to remove the branch we are on.
Of course, we have a test-case elaborate enough to verify we don't
destroy changes in submodules accidentally. Therefore I am confident
that this implementation is correct.

Fixes #49

The latter happened as now BadName is thrown, instead of BadObject.
Changes.rst was marked accordingly

Fixes #50

Previously, the implementation would gladly reset new commits in submodules,
and/or reset a dirty working tree.

Now the new force_reset/force flag has to be specified explicitly to get back
to the old behaviour.

All submodule tests except for one are working.

More to come, especially when it's about strings

All performance tests still print to stderr, but do so in a py3 compatible way