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. -- GPG-Key 0x160D1092 | tommyd3...@jabber.ccc.de | http://thomaskeller.biz Please note that according to the EU law on data retention, information on every electronic information exchange might be retained for a period of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/monotone-devel
