Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upSwitch to the new Cargo.lock format #24334
Merged
Conversation
|
Cc @jdm for deciding whether it's worth breaking third-party cargo-related tools until a Cargo stable version is aware of the new format. |
|
|
The way the Cargo.lock file is encoded on stable Rust is quite unfriendly to Git when multiple pull requests change that file at the same time, how version numbers are everywhere and all checksums are in the same place often produces merge conflicts for nothing. This patch brings the new Cargo.lock format to Servo. rust-lang/rust#63579 The main caveat is that for now, cargo-tree and similar tools won't work anymore. I checked that the duplicate crate tidy check still does its job though.
|
@jdm told me "go for it" on IRC, but I wanted a way to be able to go back first, and that's done, so LGTM: @bors-servo r=jdm |
|
|
bors-servo
added a commit
that referenced
this pull request
Oct 4, 2019
Switch to the new Cargo.lock format The way the Cargo.lock file is encoded on stable Rust is quite unfriendly to Git when multiple pull requests change that file at the same time, how version numbers are everywhere and all checksums are in the same place often produces merge conflicts for nothing. This patch brings the new Cargo.lock format to Servo. rust-lang/rust#63579 The main caveat is that for now, cargo-tree and similar tools won't work anymore. I checked that the duplicate crate tidy check still does its job though. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/24334) <!-- Reviewable:end -->
|
|
|
@bors-servo retry |
bors-servo
added a commit
that referenced
this pull request
Oct 4, 2019
Switch to the new Cargo.lock format The way the Cargo.lock file is encoded on stable Rust is quite unfriendly to Git when multiple pull requests change that file at the same time, how version numbers are everywhere and all checksums are in the same place often produces merge conflicts for nothing. This patch brings the new Cargo.lock format to Servo. rust-lang/rust#63579 The main caveat is that for now, cargo-tree and similar tools won't work anymore. I checked that the duplicate crate tidy check still does its job though. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/24334) <!-- Reviewable:end -->
|
|
This was referenced Oct 4, 2019
Merged
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.
nox commentedOct 1, 2019
•
edited
The way the Cargo.lock file is encoded on stable Rust is quite unfriendly
to Git when multiple pull requests change that file at the same time,
how version numbers are everywhere and all checksums are in the same place
often produces merge conflicts for nothing.
This patch brings the new Cargo.lock format to Servo.
rust-lang/rust#63579
The main caveat is that for now, cargo-tree and similar tools won't work
anymore.
I checked that the duplicate crate tidy check still does its job though.
This change is