Skip to content

Call for Testing of Cargo's -Z sparse-registry #3392

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
Eh2406 opened this issue Jun 22, 2022 · 3 comments
Closed

Call for Testing of Cargo's -Z sparse-registry #3392

Eh2406 opened this issue Jun 22, 2022 · 3 comments

Comments

@Eh2406
Copy link
Contributor

Eh2406 commented Jun 22, 2022

Hi,

It would be lovely to get -Z sparse-registry added to the Call for Testing section, this week or next.
internals post: https://internals.rust-lang.org/t/call-for-testing-cargo-sparse-registry/16862
tracking-issue: rust-lang/cargo#9069
rfc: https://rust-lang.github.io/rfcs/2789-sparse-index.html
unstable docs: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#sparse-registry

There will be a blog post on Inside Rust, but it is a race condition if it will be out in time for TWIR. rust-lang/blog.rust-lang.org#990

What are the next steps?

cc @rust-lang/cargo, @arlosi

@arlosi
Copy link

arlosi commented Jun 22, 2022

The blog post is up! https://blog.rust-lang.org/2022/06/22/sparse-registry-testing.html

@Eh2406
Copy link
Contributor Author

Eh2406 commented Jun 25, 2022

Tagged the RFC rust-lang/rfcs#2789 (comment)

@arlosi
Copy link

arlosi commented Jul 7, 2022

We did get mentioned in 449 so I think we can close this issue.

@Eh2406 Eh2406 closed this as completed Jul 7, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants