Re: New branch name with no other changes

Hendrik Boom <[email protected]> writes:

> On Thu, Jun 09, 2011 at 08:46:40PM +0200, Thomas Keller wrote:
>> Am 09.06.11 20:14, schrieb Hendrik Boom:
>> > I checked out a new workspace, and I want to check it in again unchenged 
>> > with a new branch name  -- the one I want to use to make changes.  I'd 
>> > like to make it clear that the new branch is starting in the same state 
>> > as the current head in the old one.
>> > 
>> > But when I try to check in, it fails:
>> > 
>> > hendrik@notlookedfor:~/fanfic/theShadowChronicles-MarkMacKinnon/edited$ 
>> > mtn commit 
>> > --branch=com.pooq.hendrik.othersfanfic.theShadowChronicles.cleanup
>> > mtn: misuse: no changes to commit
>> > 
>> > Well, yes, there were no changes in any of the files, but the branch was 
>> > different.
>> > 
>> > Is there some conceptual reason why a branch name change should not be 
>> > enough to do a commit?
>> 
>> Yes, because the branch name is not part of the revision nor the
>> manifest. Its just metadata tacked onto an already created revision. In
>> your case it should be enough to issue a new branch cert either through
>> mtn cert or mtn approve.
>> 
>> Thomas.
>
> One could argue whether this is a user-interface problem or an elegant 
> design, but I won't bother; i'm getting on with the project I'm working 
> on.

That is certainly the common result of this topic; it comes up for most
new users and they complain/ask; the get a useful answer that works but
somehow feels wrong, but they just use it and move on.

It never rises to the point of being a big enough problem to fix :).

-- 
-- Stephe