Weihang Lo

Thank you for the proposal! I totally understand what you're trying to solve. Also have no idea why Cargo implemented like this, as the logic dates back to [Cargo v0.0.1-pre]😆....

Hmm… It could be a solution but not optimal in my opinion. There are some concerns around it. - The manifest has an [already-too-long list] for each field. Personally, I...

> Would you be open to a PR that mentions in the cargo package and cargo publish docs that symlinks are followed Yeah, I think that is appreciated! Perhaps adding...

It sounds great to save bandwidth by not vendoring any dev-dependencies. However, it will be frustrating when someone tries to run `cargo test` and fails, since the de facto way...

Is it a full rebuild or rebuild from that sys crate? Also, are you using Nix? I have an assumption that one `cargo::rerun-if-changed` pointed to a directory and cargo doesn't...

The message looks worse without `CARGO_NET_GIT_FETCH_WITH_CLI=true`. ``` $ cargo +1.80.1 install --git "https://github.com/BurntSushi/utf8-ranges" --rev 11111b376b93484341c68fbca3ca110ae5cd2708 Updating git repository `https://github.com/BurntSushi/utf8-ranges` warning: spurious network error (3 tries remaining): could not read from...

> It's also interesting to note that leaving the last digit off the one-line repro actually gives a better error message with 1.80.1. This is expected btw, because Cargo check...

I can't really tell which message is worse. In 1.79 it'll fetch everything. If there are 100 tags, they will be shown all at once. In 1.80, the message “not...

Sure. When fixing a bug in Cargo, we usually write a test first that demonstrates the current buggy behavior, and passes the test suite, followed by other commits fixing both...

@BLANKatGITHUB Not sure what skills you have now. The first thing to do is following [the steps here](https://github.com/rust-lang/cargo#compiling-from-source) to compile Cargo from source. Would highly recommend reading ["Cargo Contributor Guide"](https://doc.crates.io/contrib)....