Update cargo-toml-vs-cargo-lock.md

- Improved wording ('rev' is not a line)
This commit is contained in:
4TT1L4 2022-08-25 13:50:11 +02:00 committed by GitHub
parent 9ded34a558
commit 7e6c487b9c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -43,7 +43,8 @@ could happen. There could be more commits to `regex` in the meantime, and my
build would include new commits while yours would not. Therefore, we would
get different builds. This would be bad because we want reproducible builds.
We could fix this problem by putting a `rev` line in our `Cargo.toml`:
We could fix this problem by defining a specific `rev` value in our `Cargo.toml`,
so Cargo could know exactly which revision to use when building the package:
```toml
[dependencies]