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

[Bruce Stephens]

"Steven E. Harris" <address@hidden> writes:

> Bruce Stephens <address@hidden> writes:
>
>> One might also want to commit the current workspace to an existing
>> (different) branch, but I think making that a bit more awkward is
>> fine.  (So just "mtn commit -b ..." is fine, IMHO.)
>
> But "mtn commit -b ..." would still work against a nonexistent branch,
> as it does today, right?

Sure.  No reason why it wouldn't.

I'm just suggesting trying to make smallish changes that would make
things that seem natural in (say) subversion equally natural in
monotone.

One of those seems to me to be creating a branch, then starting work
on it.  I've not used subversion much, but coming from other systems,
this difference in monotone feels just a little awkward.  

Underneath the implementation's not quite the same (in that the branch
won't actually exist in any database until I commit something to it),
but that seems OK.

(I haven't been paying attention to what "mtn branch" is supposed to
do.  I'm just dubious that it's worth making it do anything except
make a new branch and change the workspace to that.  But then I'm
dubious about the value of "clone", and I guess there's a reasonable
case for that (given that it'll more or less match the similarly named
commant in other systems).)