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

Fix errors in cargo fetch usage guide #9785

Closed
wants to merge 2 commits into from

Commits on Aug 13, 2021

  1. Be more clear about when lock files are used

    Running just `cargo build` after a `cargo fetch` *will* recheck the
    dependencies via the network. Running fetch onnly perpares the way for these
    other modes to be used withouth needing the network, it doesn't force
    subsequent commands to not use the network.
    alerque committed Aug 13, 2021
    Configuration menu
    Copy the full SHA
    c6de7f2 View commit details
    Browse the repository at this point in the history
  2. Correct default call out for cargo fetch --target

    The description section above this has the actual behaviour correctly
    called out:
    
    > If `--target` is not specified, then all target dependencies are fetched.
    
    The options text appears to have been copied from `cargo build` where it
    is valid, but the defaults for `cargo fetch` are different.
    alerque committed Aug 13, 2021
    Configuration menu
    Copy the full SHA
    a6e817c View commit details
    Browse the repository at this point in the history