Increase copypastafication of cargo search#3684
Merged
bors merged 2 commits intorust-lang:masterfrom Feb 13, 2017
Merged
Conversation
Formats the search results printed by `cargo search` so that they can be copied directly into a `Cargo.toml` file.
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
Member
|
Nice! Perhaps the |
Contributor
Author
|
Removed the |
Member
|
@bors: r+ |
Contributor
|
📌 Commit 94aa4ae has been approved by |
Contributor
|
⌛ Testing commit 94aa4ae with merge f4f264c... |
Contributor
|
💔 Test failed - status-appveyor |
Contributor
Author
|
Looks like an unrelated failure. It failed to remove a directory: |
Member
|
@bors: retry
…On Sat, Feb 11, 2017 at 8:58 PM, Casey Rodarmor ***@***.***> wrote:
Looks like an unrelated failure. It failed to remove a directory:
running 15 tests
.F.............
failures:
---- bench_default_features stdout ----
running `C:\projects\cargo\target\x86_64-pc-windows-msvc\release\cargo bench`
running `C:\projects\cargo\target\x86_64-pc-windows-msvc\release\cargo bench --no-default-features`
running `C:\projects\cargo\target\x86_64-pc-windows-msvc\release\cargo bench --bench=foo`
thread 'bench_default_features' panicked at 'failed to remove dir C:\projects\cargo\target\x86_64-pc-windows-msvc\cit\t0\foo\target\release\deps: The directory is not empty. (os error 145)', tests\cargotest\support\paths.rs:159
note: Run with `RUST_BACKTRACE=1` for a backtrace.
failures:
bench_default_features
test result: FAILED. 14 passed; 1 failed; 0 ignored; 0 measured
error: test failed
Makefile:128: recipe for target 'test-unit-x86_64-pc-windows-ms
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3684 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95NOxEDqWJ31IWyc6zzCnt1C08zSLks5rbnVXgaJpZM4L-DZu>
.
|
Contributor
|
⌛ Testing commit 94aa4ae with merge 4662d86... |
Contributor
|
💔 Test failed - status-appveyor |
Member
|
@bors: retry
…On Sun, Feb 12, 2017 at 12:05 AM, bors ***@***.***> wrote:
💔 Test failed - status-appveyor
<https://ci.appveyor.com/project/rust-lang-libs/cargo/build/1.0.1168>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3684 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95IL6cSpeDbB_iU87Vhak1UtNyRxiks5rbqESgaJpZM4L-DZu>
.
|
Contributor
bors
added a commit
that referenced
this pull request
Feb 12, 2017
Increase copypastafication of `cargo search` Formats the search results printed by `cargo search` so that they can be copied directly into a `Cargo.toml` file. I used `^`, since I like being explicit, although that seems not to be the convention, so I'd be happy to remote it. I also added a `#` in front of the description, so that that can be copy pastaed as well. I'm not super attached to this idea, but I think it's interesting, since it would serve to document what the various dependencies of a crate are for new contributors. For example: ``` $ cargo search clap clap = "^2.20.3" # A simple to use, efficient, and full featured Command Line ArgumentParser please-clap = "^0.1.0" # Pattern-match against Clap subcommands and arguments. clapcomp = "^0.1.5" # clap completion generator as command clap-test = "^0.1.1" # functions and macros to assist in testing clap structopt = "^0.0.2" # Parse command line argument by defining a struct. capgun = "^0.1.1" # fire when ready file watcher structopt-derive = "^0.0.2" # Parse command line argument by defining a struct, derive crate. cargo-outdated = "^0.3.0" # Cargo subcommand for displaying when dependencies are out of date wesers = "^0.4.1" # a simple HTTP/HTTPS server in Rust cargo-arch = "^0.1.0" # Rust Arch Linux package packer ... and 6 crates more (use --limit N to see more) ```
Contributor
|
💔 Test failed - status-appveyor |
Member
|
@bors: retry
…On Sun, Feb 12, 2017 at 1:20 PM, bors ***@***.***> wrote:
💔 Test failed - status-appveyor
<https://ci.appveyor.com/project/rust-lang-libs/cargo/build/1.0.1169>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3684 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95NkXXLmlt62dcEq903ozoMINbQZ1ks5rb1tlgaJpZM4L-DZu>
.
|
Contributor
|
⌛ Testing commit 94aa4ae with merge 4a19374... |
Contributor
|
💔 Test failed - status-appveyor |
Member
|
@bors: retry
…On Mon, Feb 13, 2017 at 11:16 AM, bors ***@***.***> wrote:
💔 Test failed - status-appveyor
<https://ci.appveyor.com/project/rust-lang-libs/cargo/build/1.0.1172>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3684 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95JLy45_FkZVl6uDWfPMZ7rbSsYkFks5rcI_dgaJpZM4L-DZu>
.
|
Contributor
bors
added a commit
that referenced
this pull request
Feb 13, 2017
Increase copypastafication of `cargo search` Formats the search results printed by `cargo search` so that they can be copied directly into a `Cargo.toml` file. I used `^`, since I like being explicit, although that seems not to be the convention, so I'd be happy to remote it. I also added a `#` in front of the description, so that that can be copy pastaed as well. I'm not super attached to this idea, but I think it's interesting, since it would serve to document what the various dependencies of a crate are for new contributors. For example: ``` $ cargo search clap clap = "^2.20.3" # A simple to use, efficient, and full featured Command Line ArgumentParser please-clap = "^0.1.0" # Pattern-match against Clap subcommands and arguments. clapcomp = "^0.1.5" # clap completion generator as command clap-test = "^0.1.1" # functions and macros to assist in testing clap structopt = "^0.0.2" # Parse command line argument by defining a struct. capgun = "^0.1.1" # fire when ready file watcher structopt-derive = "^0.0.2" # Parse command line argument by defining a struct, derive crate. cargo-outdated = "^0.3.0" # Cargo subcommand for displaying when dependencies are out of date wesers = "^0.4.1" # a simple HTTP/HTTPS server in Rust cargo-arch = "^0.1.0" # Rust Arch Linux package packer ... and 6 crates more (use --limit N to see more) ```
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
6 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.
Formats the search results printed by
cargo searchso that they can becopied directly into a
Cargo.tomlfile.I used
^, since I like being explicit, although that seems not to be the convention, so I'd be happy to remote it.I also added a
#in front of the description, so that that can be copy pastaed as well. I'm not super attached to this idea, but I think it's interesting, since it would serve to document what the various dependencies of a crate are for new contributors.For example: