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

fix: Update incorrect tracing-futures feature docs #2802

Merged
merged 3 commits into from
Nov 30, 2024

Conversation

jayvdb
Copy link
Contributor

@jayvdb jayvdb commented Nov 13, 2023

Motivation

The docs about the features is incorrect. c.f. #2799

Solution

Remove reference to feature tokio-alpha which no longer exists, and mention that feature tokio is only needed for tokio v0.1 support.

@jayvdb jayvdb requested review from hawkw, davidbarsky and a team as code owners November 13, 2023 21:20
@jayvdb jayvdb mentioned this pull request Nov 13, 2023
Copy link
Member

@davidbarsky davidbarsky left a comment

Choose a reason for hiding this comment

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

Oh, appreciate the fix.

@SpeedReach
Copy link
Contributor

CI test fail fixed in #2798

@jayvdb jayvdb force-pushed the update-tracing-futures-feature-docs branch from 20930de to 04a3436 Compare December 11, 2023 03:37
@jayvdb
Copy link
Contributor Author

jayvdb commented Dec 11, 2023

Rebased, and waiting for workflow approval for this and also for #2800

@jayvdb
Copy link
Contributor Author

jayvdb commented Sep 26, 2024

ping @mladedav , do I need to rebase this?

@mladedav
Copy link
Contributor

I think @davidbarsky just needs to get around to merging master into this and then merging this into master. I don't think this will have any conflicts so I don't think you need to rebase or manually merge anything.

@hds hds merged commit d1260a4 into tokio-rs:master Nov 30, 2024
55 checks passed
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.

5 participants