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

Explicitly mention not passing prepare flag after switching to new edition #69

Merged
merged 2 commits into from Jul 29, 2018

Conversation

Projects
None yet
2 participants
@johnthagen
Copy link
Contributor

johnthagen commented Jul 28, 2018

Related to rust-lang/cargo#5778.

Based on feedback from the internals thread, hopefully this clarification will help people realize not to pass the --prepare-for flag after they've already transitioned to the new edition.

Hopefully removes a paper cut when others test out this feature.

@alexcrichton

This comment has been minimized.

Copy link
Member

alexcrichton commented Jul 28, 2018

Thanks for the PR! I think this might be most appropriate in the section below though? After the edition is turned on we don't necessarily recommend you keep running cargo fix

@johnthagen

This comment has been minimized.

Copy link
Contributor Author

johnthagen commented Jul 29, 2018

@alexcrichton How does it look now?

@alexcrichton alexcrichton merged commit 8871e7a into rust-lang-nursery:master Jul 29, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
@alexcrichton

This comment has been minimized.

Copy link
Member

alexcrichton commented Jul 29, 2018

💯

@johnthagen johnthagen deleted the johnthagen:patch-1 branch Jul 29, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.