Weihang Lo

By the way, we might not need to move incremental into package-specific directory. Incremental directory atm * is completely opaque to cargo * seems to have per-package directories already *...

> > * Would the order of `-L` changes between different builds? > > Ideally no, the order of these flags should be deterministic. > > > * Does it...

I was looking at the wrong place. Apparently sccache hashes the cli args again and sorts them . > My thought was that the args could be sorted before they...

Could you try `git init` and see which branch name it creates? You might also like to check in your fit config files the `init.defaultBranch` value.

This seems like an upstream issue: . It might be either you don't have Apple Command-line Tools installed, or they removed the default git configuration in Sequoia. Either way, this...

@rustbot user

`1.1.0` and `1.2.0` are considered SemVer-compatible. Cargo allows only one Semver-compatible version per package. Copied from [the discussion](https://github.com/rust-lang/cargo/issues/6584#issuecomment-1308083394): > A compromise that was made way back at the beginning of...

Could you share more details of your use case? That's a better way to move forward. Changing the behavior requires an RFC, as [the comment states](https://github.com/rust-lang/cargo/issues/6584#issuecomment-1308083394). Without knowing the details,...

@teknalb this should fix the issue you mentioned in . It is not yet available in nightly, though.

> How about making `cargo` respect `.gitignore`, or alternatively, introducing `.cargoignore` when managing workspaces? @Xuanwo it already does. [The presence of `exclude` and `include` fields](https://doc.rust-lang.org/nightly/cargo/reference/manifest.html#the-exclude-and-include-fields) would affect whether `.gitignore` is...