So in my development model we aren't going to be using named branches for new
features that often.  Instead we'll be using the named branches for maint work
on old releases.  Say I have software that I use to create Fedora releases.  I
want to create a branch at each Fedora release time, so that if I have to fix
bugs for the version of that software in that Fedora release I can fix it on the
branch and issue a package update from the branch, while "default" is used for
continued new development.  Having to --force all the time feels dangerous on
the default branch.