|
From: | Ludovic Brenta |
Subject: | [Monotone-devel] [bug #17878] Usability: too easy to accidentally fork after merge or disapprove |
Date: | Sun, 09 May 2010 09:54:59 +0000 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100414 Iceweasel/3.5.9 (like Firefox/3.5.9) |
Follow-up Comment #6, bug #17878 (project monotone): That seems reasonable. Thinking more about this, "disapprove" should probably update to the parent revision of the disapproved revision; that would match the expected workflow (i.e. A | B | d fork If you disapprove B (creating d), this probably means you want to go back to A and create the fork revision). If the disapproved revision has no or multiple parents, do nothing and emit a warning. _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?17878> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |