Re: [Monotone-devel] [PATCH] mtn commit without -b and mtn branch

[Nathaniel Smith]

On Tue, Mar 06, 2007 at 04:34:29PM +0100, Thomas Keller wrote:
> The attached patch introduces a new mtn branch command and gets rid of
> the --branch option of commit. There are some FIXME notes in the patch
> where I am unsure if / how a certain thing can be done in a better way,
> just because I'm yet missing the "Big Picture".

Woo.

A thought on UI: I'm not sure that the current check that there is
_some_ common ancestor is quite the right thing.  What do people think
of:

'mtn branch':
   prints the workspace's current branch
'mtn branch <branch> --go':
   same as 'mtn update -b <branch> -r h:<branch>
'mtn branch <branch> --here':
   unconditionally sets the current workspace's branch to <branch>
'mtn branch <branch>':
   if <branch> is a new branch, or if it is an existing branch but any
   of our parents is in branch <branch>, acts like '--here'
   otherwise, errors out, suggests you hit up-arrow and add either
   --go or --here, depending on what you really expected.

? 'branch --go' at least seems like an intuitive UI...

> (PS: mailman is configured to throw away mail bodies with more than
> 40KByte, so I attached the patch gzipped.)

Not throw away -- just hold for moderation, which usually happens
every day or so :-).

-- Nathaniel

-- 
Eternity is very long, especially towards the end.
  -- Woody Allen