aboutsummaryrefslogtreecommitdiff
path: root/doc/developer-notes.md
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2018-04-11 16:20:45 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2018-04-11 16:21:10 +0200
commit6d3de17a226bf50ceb11f7703ace11c285410134 (patch)
treec5e385118c1d76c91003319f25df46edff27649f /doc/developer-notes.md
parentfb17faefb8a314b8644dea3bd063faa1cbd7ae47 (diff)
parentcab0824c96e2433a29d5e730f0e888a0a00f9eb3 (diff)
downloadbitcoin-6d3de17a226bf50ceb11f7703ace11c285410134.tar.xz
Merge #12925: wallet: Logprint the start of a rescan
cab0824 Logprint the start of a rescan (Jonas Schnelli) Pull request description: Right now, there is no log entry when a rescan starts which is confusing especially when a "still rescanning" log entry appears after the log-update timeout of 60s or when user manually aborts the rescan. This PR adds a log entry when a rescan starts. Tree-SHA512: 8712605af6fd60950bf3904cfb586da6022e44b3da6f3155fe4f02aae16df6044bc504b3d48945ea6d7fe768f0c6cb3282a2e2251d14bf3b7f1dcbd12568b05e
Diffstat (limited to 'doc/developer-notes.md')
0 files changed, 0 insertions, 0 deletions