comparison hgext/blackbox.py @ 28303:ce24de063aa5

blackbox: rewrite dirty documentation noting it is expensive
author timeless <timeless@mozdev.org>
date Tue, 01 Mar 2016 10:43:52 +0000
parents 851c41a21869
children 6b38888ab033
comparison
equal deleted inserted replaced
28302:e96a3ae025ed 28303:ce24de063aa5
9 """log repository events to a blackbox for debugging 9 """log repository events to a blackbox for debugging
10 10
11 Logs event information to .hg/blackbox.log to help debug and diagnose problems. 11 Logs event information to .hg/blackbox.log to help debug and diagnose problems.
12 The events that get logged can be configured via the blackbox.track config key. 12 The events that get logged can be configured via the blackbox.track config key.
13 13
14 If you want to record whether the repository is dirty (a `+` sign, as you'd
15 get when using :hg:`id`), you can set the blackbox.dirty config key.
16
17 Examples:: 14 Examples::
18 15
19 [blackbox] 16 [blackbox]
20 track = * 17 track = *
18 # dirty is *EXPENSIVE* (slow);
19 # each log entry indicates `+` if the repository is dirty, like :hg:`id`.
21 dirty = True 20 dirty = True
22 21
23 [blackbox] 22 [blackbox]
24 track = command, commandfinish, commandexception, exthook, pythonhook 23 track = command, commandfinish, commandexception, exthook, pythonhook
25 24