-
Notifications
You must be signed in to change notification settings - Fork 38.2k
doc: Add post branch-off note about fuzz input pruning #27574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. |
|
cc @MarcoFalke |
maflcko
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
pablomartin4btc
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK.
Btw, there's a typo on line 29 on that readme file: "corpora", since you are there also on line 32 perhaps should say "running" instead of "run".
This isn't a typo. It's a commonly used term when talking about fuzzing. |
|
@fanquake It is actually a typo, in the readme it is currently spelled "copora" not "corpora" |
|
Right. Confusion over posting the correct spelling and calling it a typo. |
|
Fixed in bitcoin-core/qa-assets#123. |
a7bbd1e doc: fix typos (fanquake) Pull request description: Pointed out in bitcoin/bitcoin#27574. ACKs for top commit: dergoegge: ACK a7bbd1e Tree-SHA512: 1c07848e641d6da58cd96eb52d188d12d00f4cabc721b020bc0a7ecd3e210ae9d0ededbb36d06e20de08d0ebd9b1899cb488059e07d3f1aa9a62ec7c38867824
No description provided.