diff options
author | fanquake <fanquake@gmail.com> | 2022-02-25 11:49:49 +0000 |
---|---|---|
committer | fanquake <fanquake@gmail.com> | 2022-02-25 11:50:10 +0000 |
commit | 0dc1002c30124a67a3146e10b16dd1d391445066 (patch) | |
tree | cc04d002e581deb5b23a1f925c231987da17e725 /REVIEWERS | |
parent | b00b60ed4f27066656e45635f1386e6b1550c6ed (diff) | |
parent | fa694f61ab21cb973843e5234a6aeacd4a957e05 (diff) | |
download | bitcoin-0dc1002c30124a67a3146e10b16dd1d391445066.tar.xz |
Merge bitcoin/bitcoin#24433: doc: Explain that feedback needs to be addressed
fa694f61ab21cb973843e5234a6aeacd4a957e05 doc: Explain that feedback needs to be addressed (MarcoFalke)
fa0819eea380047c9d7404895d3e4e8ea37930bb doc: Move peer-review paragraph to right section (MarcoFalke)
fa2b65b3583e7e7ffa892bf2453720b0d2bd7904 doc: Add link to release-process.md in CONTRIBUTING.md (MarcoFalke)
Pull request description:
Generally, the pull request author is expected to reply to all comments or iterate the code before merge. Of course, it is allowed to reject feedback, but it should not be done by silently ignoring it.
Clarify this in the docs.
Also, some minor copy edits.
ACKs for top commit:
michaelfolkson:
ACK fa694f61ab21cb973843e5234a6aeacd4a957e05
Sjors:
ACK fa694f61ab21cb973843e5234a6aeacd4a957e05
jamesob:
ACK https://github.com/bitcoin/bitcoin/pull/24433/commits/fa694f61ab21cb973843e5234a6aeacd4a957e05
prayank23:
ACK https://github.com/bitcoin/bitcoin/pull/24433/commits/fa694f61ab21cb973843e5234a6aeacd4a957e05
brunoerg:
ACK fa694f61ab21cb973843e5234a6aeacd4a957e05
w0xlt:
ACK fa694f6
Tree-SHA512: 339d6f252395664442f4bfb73d839314de8c9b0fdc8900a1c4a67b1cef9c73ecb98c7587a842dd5a36a4a3efbd8270d2162962013893706313f7ef34491db18c
Diffstat (limited to 'REVIEWERS')
0 files changed, 0 insertions, 0 deletions