Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Jump to bottom

Using git to manage cargo.io-index may be not good solution. #9413

Closed
ghost opened this issue Apr 25, 2021 · 1 comment
Closed

Using git to manage cargo.io-index may be not good solution. #9413

ghost opened this issue Apr 25, 2021 · 1 comment
Labels
C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`

Comments

@ghost
Copy link

ghost commented Apr 25, 2021

The bad part of git, large space waste( History will growth, and waste user diskspace)
and git does not support continue download, if the download break. their be much more problem with it.

warning: spurious network error (2 tries remaining): failed to read data: 服务器返回的信息无效或不可识别
@ghost ghost added the C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` label Apr 25, 2021
@Eh2406
Copy link
Contributor

Eh2406 commented Apr 25, 2021

There are meny advantages to the way we use git. Most of the disadvantages we have mitigations for. But there is work being done to build a new way. rust-lang/rfcs#2789

@Eh2406 Eh2406 closed this as completed Apr 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Eh2406