Eric Huss

There seems to be a discussion up at https://github.com/rust-lang/cargo/pull/10330#discussion_r794815070 that doesn't appear to be resolved. I don't think the `--target` flag requirement can just be removed without major effort. There's...

Hm, I was perhaps not understanding the intent of the per-package-target feature. I did not realize that it doesn't work with dependencies at all. That doesn't match the motivation for...

@jguhlin Is this still a problem if you don't use `CARGO_NET_GIT_FETCH_WITH_CLI`? Or was this some transient issue?

If you'd like to help us debug this, can you try running with the environment variables `CARGO_HTTP_DEBUG=true` and `CARGO_LOG=cargo::ops::registry=trace` set? That should display some debug information about the network traffic....

It looks like you are using a proxy (iaa-proxy.uod.otago.ac.nz), was that intentional? Do you happen to know what software it is running? You can try setting the `CARGO_HTTP_MULTIPLEXING=false` environment variable....

I personally would lean towards option 3b. I wouldn't think the scenario of directly executing cargo without rustup, but wanting rustc to be driven by rustup is too common (mostly...

I'm not sure, but I think this was just an oversight. My original intent mentioned in https://github.com/rust-lang/cargo/pull/8441#issuecomment-659013313 was that it applied to unittests as well: ``` cargo:rustc-link-arg-tests=… # equivalent to...

@Eh2406 `[patch]` with a `path` dependency will also issue warnings.

The decision to show warnings is controlled by [`show_warnings`](https://github.com/rust-lang/cargo/blob/580461bd40ae91321679c34554c7a7748e18077e/src/cargo/core/compiler/unit.rs#L93-L97). However, whether or not something comes from `[patch]` is lost by the time it is needed, so I think adding that...

Thanks! @bors r+