Skip to content
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

refactor: remove in-code warning suppression #28002

Merged
merged 1 commit into from Jun 30, 2023

Conversation

fanquake
Copy link
Member

Should no-longer be needed post #27872. If it is, then suppress-external-warnings should be fixed.

Should no-longer be needed post bitcoin#27872. If it is, then
suppress-external-warnings should be fixed.
@DrahtBot
Copy link
Contributor

DrahtBot commented Jun 29, 2023

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Reviews

See the guideline for information on the review process.

Type Reviewers
ACK hebasto

If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

Copy link
Member

@hebasto hebasto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK 3210f22

@fanquake fanquake merged commit b5ebeb3 into bitcoin:master Jun 30, 2023
15 checks passed
@fanquake fanquake deleted the in_code_warn_suppress branch June 30, 2023 08:45
sidhujag pushed a commit to syscoin/syscoin that referenced this pull request Jun 30, 2023
3210f22 refactor: remove in-code warning suppression (fanquake)

Pull request description:

  Should no-longer be needed post bitcoin#27872. If it is, then suppress-external-warnings should be fixed.

ACKs for top commit:
  hebasto:
    ACK 3210f22

Tree-SHA512: 2405250b7308779d576f13ce9144944abd5b2293499a0c0fe940398dae951cb871246a55c0e644a038ee238f9510b5845c3e39f9658d9f10225a076d8122f078
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants