-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
doc(features2): polish docs a bit #11185
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
r? @ehuss (rust-highfive has picked a reviewer for you, use r? to override) |
rust-highfive
added
the
S-waiting-on-review
Status: Awaiting review from the assignee but also interested parties.
label
Oct 7, 2022
weihanglo
force-pushed
the
features2-docs
branch
from
October 7, 2022 10:41
24ec0b4
to
6b8903e
Compare
@bors r+ |
bors
added
S-waiting-on-bors
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
and removed
S-waiting-on-review
Status: Awaiting review from the assignee but also interested parties.
labels
Oct 7, 2022
☀️ Test successful - checks-actions |
weihanglo
added a commit
to weihanglo/rust
that referenced
this pull request
Oct 7, 2022
4 commits in 0b84a35c2c7d70df4875a03eb19084b0e7a543ef..3cdf1ab25dc4fe56f890e8c7330d53a23ad905d3 2022-10-03 19:13:21 +0000 to 2022-10-07 17:34:03 +0000 - fix(test): Distinguish 'testname' from escaped arguments (rust-lang/cargo#11190) - Fix sparse registry lockfile urls containing 'registry+sparse+' (rust-lang/cargo#11177) - doc(features2): polish docs a bit (rust-lang/cargo#11185) - Import `cargo remove` into cargo (rust-lang/cargo#11099)
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Oct 7, 2022
Update cargo 4 commits in 0b84a35c2c7d70df4875a03eb19084b0e7a543ef..3cdf1ab25dc4fe56f890e8c7330d53a23ad905d3 2022-10-03 19:13:21 +0000 to 2022-10-07 17:34:03 +0000 - fix(test): Distinguish 'testname' from escaped arguments (rust-lang/cargo#11190) - Fix sparse registry lockfile urls containing 'registry+sparse+' (rust-lang/cargo#11177) - doc(features2): polish docs a bit (rust-lang/cargo#11185) - Import `cargo remove` into cargo (rust-lang/cargo#11099)
RalfJung
pushed a commit
to RalfJung/miri
that referenced
this pull request
Oct 9, 2022
Update cargo 4 commits in 0b84a35c2c7d70df4875a03eb19084b0e7a543ef..3cdf1ab25dc4fe56f890e8c7330d53a23ad905d3 2022-10-03 19:13:21 +0000 to 2022-10-07 17:34:03 +0000 - fix(test): Distinguish 'testname' from escaped arguments (rust-lang/cargo#11190) - Fix sparse registry lockfile urls containing 'registry+sparse+' (rust-lang/cargo#11177) - doc(features2): polish docs a bit (rust-lang/cargo#11185) - Import `cargo remove` into cargo (rust-lang/cargo#11099)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
S-waiting-on-bors
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR try to resolve?
Polish docs of the new feature resolver v2 a bit.
How should we test and review this PR?
And read.
Additional information
I can't find any assumption to add at this moment. If ehuss can recall that would be awesome!