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

[Nathaniel Smith]

On Sun, Nov 11, 2007 at 09:13:14PM -0800, Zack Weinberg wrote:
> As someone who habitually edits _MTN/options to get this effect, may I
> add that it would be really nice if this sequence
> 
> # workspace is on branch foo.bar, but not at its head
> $ mtn branch foo.bar.newbranch
> $ mtn update
> 
> brought the workspace to the head of foo.bar, without changing the
> selection of foo.bar.newbranch for a subsequent commit.  (This is
> *not* what happens now; you get an error message, have to say
> -rh:foo.bar, and then you lose the .newbranch selection.  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?

Alternatively, it occurs to me that in the presence of
workspace-merge, merge -r h:parent-branch can probably accomplish what
you want.

-- Nathaniel

-- 
"Of course, the entire effort is to put oneself
 Outside the ordinary range
 Of what are called statistics."
  -- Stephan Spender