Re: [Monotone-devel] more on commit without -b option

[Zack Weinberg]

On Nov 11, 2007 9:25 PM, Nathaniel Smith <address@hidden> wrote:
> > To make this
> > more motivated, consider setting .newbranch, going away for a few
> > days, and then wanting to update to the latest baseline before you
> > start hacking.)
>
> I sympathize with the use case.  Before we implement it, can you
> propose a few-sentence description for the manual that will make this
> behavior clear to the meanest intelligence?

"Starting a new branch with @command{mtn branch} only affects the
behavior of a subsequent @command{mtn commit}.  All other commands
treat the workspace as associated with the same branch as before the
@command{mtn branch} was issued."

In terms of _MTN/options, I imagine something like

branch "foo.bar"
commitbranch "foo.bar.newbranch"

where commitbranch overrides branch only for commit.  It's possible
that some other commands should also look at commitbranch but right
now I can't think of any.

zw