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

Make cargo-binstall instructions consistent #1243

Merged
merged 1 commit into from
Jan 11, 2024
Merged

Conversation

zaurask
Copy link
Contributor

@zaurask zaurask commented Jan 11, 2024

Small change to make cargo-binstall instructions consistent after adding them in #1239.
(Following the instructions I was confused and actually checked whether cargo-quickinstall installs cargo-binstall...)

@@ -161,7 +161,7 @@ Our [stability guide] helps to judge how much churn can be expected when dependi

### Download a Binary Release

Using `cargo binstall`, one is able to fetch [binary releases][releases]. You can install it via `cargo install cargo-quickinstall`, assuming
Using `cargo binstall`, one is able to fetch [binary releases][releases]. You can install it via `cargo install cargo-binstall`, assuming
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can link to the cargo-binstall installation sector which provides binary installation.

Sorry I forgot this when editing the file.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And I missed it in the review :/!

Copy link
Member

@Byron Byron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks so much for the fix, and apologies for the confusion this caused.

@Byron Byron merged commit 79fd006 into GitoxideLabs:main Jan 11, 2024
3 checks passed
@zaurask zaurask deleted the patch-1 branch January 11, 2024 08:22
@zaurask
Copy link
Contributor Author

zaurask commented Jan 11, 2024

No problem, the confusion part was meant as a motivation for the change not to complain 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants