Nathaniel Smith <[EMAIL PROTECTED]> writes: > On Tue, Jun 24, 2008 at 08:43:40AM -0400, Stephen Leake wrote: >> My actual use case was this: if I have a workspace that is nominally >> at the head of branch 'main', and I start messing around, then realize >> I really should be working on branch 'experimental', I want to do: >> >> mtn "just switch to experimental, and don't bother me!" >> >> which is approximated by: >> >> mtn ls --missing > files_i_deleted.log >> mtn revert --missing >> mtn update --branch experimental >> some_painful_shell_script.sh files_i_deleted.log >> >> I'd rather just do 'mtn update --branch experimental' :). > > I'm not sure I follow what you want, but it sounds like > mtn drop --missing > mtn update -r h:experimental > should do it?
You are right. I was somehow thinking that 'mtn drop --missing' would influence the main branch; but 'mtn commit' is not needed here. I guess I'm still transitioning from 15 years of CVS usage :(. -- -- Stephe _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
