< bitcoin-git> [bitcoin] jadijadi opened pull request #20769: net: fixes #20657 - Advertised address where nobody is listening (master...fixes-issue-20657) https://github.com/bitcoin/bitcoin/pull/20769
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #20771: refactor: Enable -Wswitch for FeeEstimateHorizon (master...2012-WswitchFeeEstimateHorizon) https://github.com/bitcoin/bitcoin/pull/20771
< jonatack> Is there a reason why we don't have help for CLI options? e.g. ./src/bitcoin-cli help -getinfo, ./src/bitcoin-cli help -netinfo
< jonatack> (if not, is there a already planned way to add the help doc / would it be a good idea?)
< jonatack> (for more detailed help than in ./src/bitcoin-cli -h)
< jonatack> I was thinking it might be good to have a detailed help doc for -netinfo, either with "help -netinfo", or expand the existing one at "./src/bitcoin-cli -h | grep -A3 netinfo", or add a doc/netinfo.md file
< emzy> jonatack: I agree.
< harding> help <command> is for RPCs; -h is for a quick summary of CLI parameters. Extended CLI parameter help should probably be in a manual page.
< CryptoKid> Verry Fast bitcoin miner ! https://cryptotabbrowser.com/16879401 for crypto miners
< CryptoKid> Verry Fast bitcoin miner ! https://cryptotabbrowser.com/16879401 for crypto miners
< bitcoin-git> [bitcoin] mjdietzx opened pull request #20772: fuzz: bolster ExtractDestination(s) checks (master...test-fuzz-extract-destinations) https://github.com/bitcoin/bitcoin/pull/20772
< bitcoin-git> [bitcoin] S3RK opened pull request #20773: refactor: split CWallet::Create (master...refactor_wallet_create) https://github.com/bitcoin/bitcoin/pull/20773
< bitcoin-git> [bitcoin] multisignature opened pull request #20774: Update README.md (master...master) https://github.com/bitcoin/bitcoin/pull/20774
< bitcoin-git> [bitcoin] mjdietzx opened pull request #20775: [POC/DRAFT] - Finalize remove reqsigs deprecation from rpcs (master...finalize-remove-reqsigs-from-rpcs) https://github.com/bitcoin/bitcoin/pull/20775
< jonatack> emzy: harding: thanks. yes. for now i updated the -h summary help to say it that in addition to the optional integer for the level of details, it also takes "help" as an argument to get a detailed help
< harding> jonatack: that seems reasonable.
< jonatack> e.g. bitcoin-cli -netinfo help
< jonatack> and we'll see what reviewers say
< phantomcircuit> jonasschnelli, confusingly there's also actually another thing called a seed, which is when you start from scratch
< sipa> libfuzzer'a documentation refers to the files in the data directory as "sample inputs" actually, not needs
< sipa> it does say fuzzing works better if the directory contains "initial seeds" to start from
< phantomcircuit> sipa, yeah but it also has a seed which is actually closer to what jonasschnelli was talking about
< sipa> yeah
< sipa> but maybe we shouldn't be referring to the contents of our corpus as "seeds" but as "inputs"
< phantomcircuit> sipa, probably shouldn't be
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/43fc7a569c13...02cf20b9f571
< bitcoin-git> bitcoin/master 667d203 Amiti Uttarwar: [doc] Add permissions to the getpeerinfo help.
< bitcoin-git> bitcoin/master 02cf20b MarcoFalke: Merge #20756: [doc] Add missing field (permissions) to the getpeerinfo hel...
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #20756: [doc] Add missing field (permissions) to the getpeerinfo help (master...2020-12-getpeerinfo-permissions) https://github.com/bitcoin/bitcoin/pull/20756
< bitcoin-git> [bitcoin] jonatack opened pull request #20778: net, p2p, gui: replace direction with connection type in gui peer details window (master...display-peer-conn-types) https://github.com/bitcoin/bitcoin/pull/20778