mirror of
https://github.com/bitcoin/bitcoin.git
synced 2026-04-14 01:27:24 +02:00
fa45a1503elog: Use LogWarning for non-critical logs (MarcoFalke)fa0018d011log: Use LogError for fatal errors (MarcoFalke)22229de728doc: Fix typo in init log (MarcoFalke) Pull request description: Logging supports severity levels above info via the legacy `LogPrintf`. So use the more appropriate `LogError` or `LogWarning`, where it applies. This has a few small benefits: * It often allows to remove the manual and literal "error: ", "Warning:", ... prefixes. Instead the uniform log level formatting is used. * It is easier to grep or glance for more severe logs, which indicate some kind of alert. * `LogPrintf` didn't indicate any severity level, but it is an alias for `LogInfo`. So having the log level explicitly spelled out makes it easier to read the code. * Also, remove the redundant trailing `\n` newline, while touching. * Also, remove the `__func__` formatting in the log string, which is redundant with `-logsourcelocations`. Instead, use a unique log string for each location. ACKs for top commit: l0rinc: Code review ACKfa45a1503estickies-v: ACKfa45a1503erkrux: crACKfa45a1503eTree-SHA512: 516d439c36716f969c6e82d00bcda03c92c8765a9e41593b90052c86f8fa3a3dacbb2c3dc98bfc862cefa54cae34842b488671a20dd86cf1d15fb94aa5563406