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

[Dirkjan Ochtman]

On Thu, Sep 17, 2009 at 21:36, Sune Foldager <cryo at cyanite.org> wrote:
> # HG changeset patch
> # User Sune Foldager <sune.foldager at edlund.dk>
> # Date 1249889760 -7200
> # Node ID 01de02eadec5f88a19bbeca3e9f57dc036422ef2
> # Parent  de414835d1405ccec77f6cc5211859368ae8274f
> named branches: --newbranch option to allow intial push of new branches
>
> Compare this to --force which allows anything to be pushed. With --newbranch,
> only changesets to named branches not present on the remote are allowed.

Why not allow changesets on other branches in the same push? Without
-r, this behavior seems like it might be pretty confusing for people.

Also, I think the option would have to be named --new-branch.

I do much like the idea of finally getting rid of requiring --force
for this one, though!

Cheers,

Dirkjan