chgserver: document why we don't merge mtimehash and confighash
People may get confused about chg's mtimehash and confighash design: why two
hashes instead of just one. This patch adds text addressing the concern.
--- a/hgext/chgserver.py Thu Jun 30 10:31:50 2016 +0100
+++ b/hgext/chgserver.py Wed Jun 29 23:53:20 2016 +0100
@@ -154,6 +154,10 @@
for chgserver, it is designed that once mtimehash changes, the server is
considered outdated immediately and should no longer provide service.
+
+ mtimehash is not included in confighash because we only know the paths of
+ extensions after importing them (there is imp.find_module but that faces
+ race conditions). We need to calculate confighash without importing.
"""
def trystat(path):
try: