On Tue, 20 Apr 2010 03:56:29 -0400 Stephen Leake wrote: > Zack Weinberg <za...@panix.com> writes: > > and makes the shell command interface less usable. Things like "mtn up > > -r <revision not on the current branch>" really must continue to > > modify _MTN/options. > > I never do that; it's not part of my workflow.
Another opinion here: I pretty much rely on "mtn up -r <revision not on the current branch>" remembering the new branch, so I would like it to stay the way it currently is. > I do "mtn up -r", but if the revision is accidently from a different > branch, I'd like mtn to fail with an error about changing branches (to > catch accidental violations of the workflow), and require an explicit > option to make it work (to recover from violations). Would this be possible via some Lua hook? -- Tero Koskinen <tero.koski...@iki.fi> _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
