On Thu, Jun 25, 2009 at 1:01 AM, Colin Caughie<c.caug...@indigovision.com> wrote: >> -----Original Message----- >> From: Doug Philips [mailto:d...@mac.com] >> Sent: 24 June 2009 20:54 >> To: Steve Borho >> Cc: tortoisehg-discuss@lists.sourceforge.net >> Subject: Re: [thg] One week to go >> >> On or about Wednesday, June 24, 2009, at 03:45PM, Steve Borho >> indited: >> >2) Enabling this feature is a non-trivial step, and I prefer to >> >require people to RTFM and understand what it is exactly that they >> are >> >enabling. > > OK that's fair enough. > >> Thank you. I don't want to have to tell my team not to enable it. >> Part of the problem with that option is that it seems to simple, and >> yet it can cause -such- havoc. :( > > I've certainly seen it cause havoc if some people working on a repo have it > enabled and others don't. Is this what you mean? I guess that in itself is a > good reason not to have TortoiseHG make it easy to enable. The last SCM tool > we used had line ending conversion enabled by default and made it difficult > to turn off, so that was never a problem. > > Perhaps the solution for us would be to create a custom installer for our > organization that doesn't give the option _not_ to install it; that way > there's less chance that someone can mess up the repo having different > settings from everyone else.
If your organization has a policy that the extension should always be enabled with a specific filter set, then by all means create a custom installer with a Mercurial.ini that has the configuration you desire. Or perhaps package the installer with a batch file that enforces your policies. I see no problem with that at all. -- Steve Borho ------------------------------------------------------------------------------ _______________________________________________ Tortoisehg-discuss mailing list Tortoisehg-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
