When a TortoiseHg "Refresh status..." starts, in a working directory of our main repo, it takes several minutes to complete [*]. This is very disruptive to workflow, so I would like to understand what could trigger TortoiseHg to refresh its status.
For example, I can imagine that changes to the following might trigger a refresh: - .hg/hgrc - personal mercurial.ini - and any files included by those If that's true, how selective is the refresh? For example, if one turned on hgeol, a refresh would be required. But if one changed IssueTracking settings only (tortoisehg.issue.regex or tortoisehg.issue.link), would a "Refresh status..." be required? (How clever is it at analysing the nature of the changes) And what about commits, pushes, pulls and updates - do they all trigger checks? So, is there any list or documentation anywhere that says what triggers "Refresh status..." please? Thanks Clare (TortoiseHg 2.4.1, Windows 7 Pro) [*] in fact, 18 minutes and still counting, on a very fast PC... LEGAL NOTICE Unless expressly stated otherwise, information contained in this message is confidential. If this message is not intended for you, please inform [email protected] and delete the message. The Cambridge Crystallographic Data Centre is a company Limited by Guarantee and a Registered Charity. Registered in England No. 2155347 Registered Charity No. 800579 Registered office 12 Union Road, Cambridge CB2 1EZ. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
