New issue 104: Synchronize dialog's super-cache of URL paths, is it too much? http://bitbucket.org/tortoisehg/stable/issue/104/synchronize-dialogs-super-cache-of-url-paths-is-it-too
Doug Philips / dgou on Mon, 16 Mar 2009 19:51:23 +0100: Description: The issue here is that when the user is working in repo R1, the URL paths from that repo are added to the global (per user?) synch cache. Then when user switches to working in repo R2, the URL paths from repo R1 are also presented. In the Mercurial "repos as branches" work flow, this can easily cause confusion and lead to accidental pushes to the wrong tree. This does not happen with the command line since command line Mercurial use does not have this cache. Steve pointed out in email that having the super-cache might be helpful for the clone dialog. A few possible resolutions: a) This is desired behavior, won't fix. b) Do what CLI Hg does and don't keep super-cache for synchronize. c) segregate the URL paths in the drop down to put the "other repo" paths in another section. My feeling is that the only paths that should show up in the synchronize dialog for a repo should be those defined in that repo, or in the global config only. Options for paths in the clone dialog are a separate issue. Responsible: tortoisehg -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
