Add --release flag to cargo doc
#1973
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? @wycats (rust_highfive has picked a reviewer for you, use r? to override) |
While this may not necessarily make sense all the time, this enables Cargo to not rebuild anything if a `cargo build --release` was previously executed.
alexcrichton
force-pushed
the
cargo-doc-release
branch
from
b5a1cc7
to
576ddf3
Compare
|
r? @brson |
|
@bors r+ |
|
📌 Commit 576ddf3 has been approved by |
bors
added a commit
that referenced
this pull request
Sep 8, 2015
While this may not necessarily make sense all the time, this enables Cargo to not rebuild anything if a `cargo build --release` was previously executed.
|
☀️ Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64 |
This was referenced Sep 8, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While this may not necessarily make sense all the time, this enables Cargo to
not rebuild anything if a
cargo build --releasewas previously executed.