Tracking Issue for source replacement ambiguity

[ehuss]

Summary

RFC: #3289
Implementation: #10907
Documentation: https://doc.rust-lang.org/nightly/cargo/reference/source-replacement.html

This RFC is to resolve the interaction of source-replacement and registry API operations like publishing.

Unresolved Issues

• Should the --registry <NAME> command line argument be allowed to reference the name of a source from the [source] table as well? Resolved: At this time, --registry does not support [source] names. (However, [source] replace-with can reference [registries] names. So there is some overlap.

Future Extensions

No response

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

[arlosi]

@ehuss could you update the Implementation link to #10907

[ehuss]

Closing as I believe this is resolved by #10907.