On 19.09.2009 06:48, Yuki KODAMA wrote: > On Sat, Sep 19, 2009 at 11:36, Steve Borho <st...@borho.org> wrote: >> On Fri, Sep 18, 2009 at 12:21 AM, Yuki KODAMA <endflow....@gmail.com> wrote: >> >> Actually, my commit was wrong. Specifying --check prevents you from >> doing any update if the working directory is dirty, even if you're not >> switching branches. >> >> So both --clean and --check need to be checkboxes, or we need radio >> buttons with 'force clean', 'check clean', 'allow merge'.. or >> something similar. > > Attached patch provides update options more explicitly. > I know this is not needed any more, but I send for something... > No need to apply this patch to main repo, Steve.
I want this. Please apply it. We could use it until we have something better in place and is working. Also it doesn't hurt to have it in the history, so I can hg update back to it and use :) > Now I'm trying to implement Steve's idea: smart update features. Thank you for working on that. I agree with doing Steve's idea. I have a bit strange feelings though that we need to put that much logic on top of mercurial, but this is probably not the fault of TortoiseHg. And TortoiseHg is in the lucky position of being able to do it. Thanks to the interactive userinterface. Maybe mercurial has just too many constraints to fulfill (command line backwards compatibility) so it is harder to improve there. Also command line lacks the interactiveness of an UI. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
