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

remove dependency on tracing's log feature #2342

Merged
merged 1 commit into from
Nov 25, 2020

Conversation

mikeyhew
Copy link
Contributor

fixes #2326

I wasn't sure what the right way to update the changelog was, so I just used my best guess. Let me know if I should do something differently.

@mikeyhew
Copy link
Contributor Author

how do I see the gitcop error message? The link just goes to https://gitcop.com/

@seanmonstar
Copy link
Member

seanmonstar commented Nov 24, 2020

Thanks! You can leave the changelog update out, those are automatically construct with a script at release time. And don't worry about gitcop, it's not marked a "required" check, it's just a reminder to me to make the commit message fit the aforementioned script requirements when I squash-merge.

@mikeyhew
Copy link
Contributor Author

OK, I've removed the changelog update.

@seanmonstar seanmonstar merged commit db32e10 into hyperium:master Nov 25, 2020
@seanmonstar
Copy link
Member

Thanks!

BenxiangGe pushed a commit to BenxiangGe/hyper that referenced this pull request Jul 26, 2021
)

Closes hyperium#2326

BREAKING CHANGE: hyper no longer emits `log` records automatically.
  If you need hyper to integrate with a `log` logger (as opposed to `tracing`),
  you can add `tracing = { version = "0.1", features = ["log"] }` to activate them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove log feature of tracing
2 participants