From 8f99c700ff3ceb59d83d4653427105b80d16f266 Mon Sep 17 00:00:00 2001 From: Jan Zerebecki Date: Tue, 27 Sep 2016 23:11:50 +0200 Subject: [PATCH] Document how to cargo-update to a specific version Closes #13310 --- docs/HACKING_QUICKSTART.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/HACKING_QUICKSTART.md b/docs/HACKING_QUICKSTART.md index e0d96b547ea..ec65d263d86 100644 --- a/docs/HACKING_QUICKSTART.md +++ b/docs/HACKING_QUICKSTART.md @@ -94,7 +94,7 @@ name = "stb_image" source = "git+https://github.com/servo/rust-stb-image#f4c5380cd586bfe16326e05e2518aa044397894b" ``` -This file should not be edited by hand. In a normal Rust project, to update the git revision, you would use `cargo update -p stb_image`, but in Servo, use `./mach cargo-update -p stb_image`. +This file should not be edited by hand. In a normal Rust project, to update the git revision, you would use `cargo update -p stb_image`, but in Servo, use `./mach cargo-update -p stb_image`. Other arguments to cargo are also understood, e.g. use --precise '0.2.3' to update that crate to version 0.2.3. See [Cargo's documentation about Cargo.toml and Cargo.lock files](http://doc.crates.io/guide.html#cargotoml-vs-cargolock).