Support rustup-init --default-toolchain none#1257
Merged
Merged
Conversation
Contributor
Author
|
ping @Diggsey @alexcrichton |
Member
|
@petrochenkov oh oops sorry, thanks for the ping! Just to clarify, what's the behavior of the rustc/cargo/etc shims in this scenario? If you avoid installing a toolchain, what does |
Contributor
Author
|
Member
|
Ok sounds great! @bors: r+ |
Contributor
|
📌 Commit d93c1c8 has been approved by |
Contributor
bors
added a commit
that referenced
this pull request
Oct 6, 2017
Support `rustup-init --default-toolchain none` To address this use case #309 (comment). This is especially useful when user directories have quotas into which large components (e.g. docs) do not fit.
Contributor
|
☀️ Test successful - status-appveyor, status-travis |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
To address this use case #309 (comment).
This is especially useful when user directories have quotas into which large components (e.g. docs) do not fit.