In message <[EMAIL PROTECTED]> on Sat, 24 Feb 2007 07:14:31 +1100, William Uther <[EMAIL PROTECTED]> said:
willu> Then I went to put it on a branch: willu> willu> % cd monotone-newcmds willu> % mtn ci -b net.venge.monotone.new-commands -m "start a branch for willu> new commands" willu> mtn: misuse: no changes to commit willu> willu> I'm not sure how I feel about that. I can see why the check is willu> there, and I'm guessing there are two ways around it: willu> willu> i) make some changes first :) willu> ii) create some new cert so that the old revision is on both willu> the old and new branches, then update the wc to the new willu> branch. willu> willu> I figured i) was easier. Actually, monotone could use a subcommand such as "newbranch", with the only purpose to change _MTN/options with the name of the new branch. In the mean time, you can actually do that change manually. Yes, it' a hack, but a pretty harmless one ;-). willu> I think partial pull is more of an issue for new users than willu> security. Someone is currently working on partial pull. Cheers, Richard ----- Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. -- Richard Levitte [EMAIL PROTECTED] http://richard.levitte.org/ "When I became a man I put away childish things, including the fear of childishness and the desire to be very grown up." -- C.S. Lewis _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
