mirrors/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2025-03-13 11:35:20 +01:00
Code Issues Projects Releases Wiki Activity

Merge b7aae361b2 into a50af6e4c4

Browse source
This commit is contained in:
Ryan Ofsky 2025-03-13 02:03:46 +01:00 • committed by GitHub
commit eb520a234e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
doc/developer-notes.md
View file

@ -26,6 +26,7 @@ Developer Notes
- [Ignoring IDE/editor files](#ignoring-ideeditor-files) - [Ignoring IDE/editor files](#ignoring-ideeditor-files)
- [Development guidelines](#development-guidelines) - [Development guidelines](#development-guidelines)
- [General Bitcoin Core](#general-bitcoin-core) - [General Bitcoin Core](#general-bitcoin-core)
- [Logging](#logging)
- [Wallet](#wallet) - [Wallet](#wallet)
- [General C++](#general-c) - [General C++](#general-c)
- [C++ data structures](#c-data-structures) - [C++ data structures](#c-data-structures)
@ -756,14 +757,13 @@ logging messages. They should be used as follows:
attacker to fill up storage. Note that `LogPrintf(fmt, params...)` is attacker to fill up storage. Note that `LogPrintf(fmt, params...)` is
a deprecated alias for `LogInfo`. a deprecated alias for `LogInfo`.
- `LogError(fmt, params...)` should be used in place of `LogInfo` for - `LogError(fmt, params...)` should be used in place of `LogInfo` for severe
severe problems that require the node (or a subsystem) to shut down errors the node admin will need to address (e.g., failure to write data).
entirely (e.g., insufficient storage space).
- `LogWarning(fmt, params...)` should be used in place of `LogInfo` for - `LogWarning(fmt, params...)` should be used in place of `LogInfo` for
severe problems that the node admin should address, but are not unexpected conditions indicating potentially severe problems the node admin
severe enough to warrant shutting down the node (e.g., system time should address (e.g. system time appears to be wrong, unknown soft fork
appears to be wrong, unknown soft fork appears to have activated). appears to have activated).
- `LogTrace(BCLog::CATEGORY, fmt, params...)` should be used in place of - `LogTrace(BCLog::CATEGORY, fmt, params...)` should be used in place of
`LogDebug` for log messages that would be unusable on a production `LogDebug` for log messages that would be unusable on a production