[PATCH 1 of 1] named branches: --newbranch option to allow intial push of new branches

[Sune Foldager]

> How does this handle the use case, when say the default branch has
> been merged with some named branch foo, and then a changeset is
> committed to foo and pushed, thus creating a new head, but not a new
> branch?

This is already handled in the current version, by I previous patch we got pushed a while back :-).

> My personal opinion is that no special option should be required [...]

It works just like that :-).

/Sune