On Fri, Aug 28, 2009 at 12:50 PM, Adrian Buehlmann<adr...@cadifra.com> wrote: > On 28.08.2009 19:15, Steve Borho wrote: >> There's a lot of rather advanced features being tacked onto the >> changelog and commit tools on the last few months, which is all fine >> and grand for experienced Mercurial users, but I'm beginning to wonder >> if we want to hide many of these commands by default to protect new >> users from shooting themselves in the feet. >> >> Specifically: rebase, strip, transplant, backout, MQ >> >> Many of those operations have failure modes that require command line >> manipulations to get back to a normal working state. >> >> I'm curious how other people feel about this. > > I'm fine with not showing these by default, turning them > on with some expert mode -- or something.
Yeah, either through 'tortoisehg.trainingwheels = False' or just checking for loaded extensions. > backout and rebase seem rather harmless though (compared to strip). Backout is mostly harmless, though potentially confusing. When there are conflicts, rebase requires you to resolve conflicts and then run 'hg rebase --continue' on the command line to finish the transaction. > Is the strip command hidden if mq extension has not been turned on? > (I tried disabling mq in my mercurial.ini, but the strip command > is still there in hgtk log...) strip is always shown in hgtk log. The MQ features in the commit tool are hidden unless the MQ extension is loaded, however. -- Steve Borho ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tortoisehg-discuss mailing list Tortoisehg-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
