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

Bump redox_users; Disable redox_users default features #7

Merged
merged 1 commit into from
Aug 27, 2020
Merged

Bump redox_users; Disable redox_users default features #7

merged 1 commit into from
Aug 27, 2020

Conversation

MggMuggins
Copy link
Contributor

I just released a new version of redox_users with argon behind a feature flag (enabled by default). There had been some buzz a while back about the size of the dependency tree for this crate and dirs earlier, so I've finally gotten around to doing my bit.

I just released a new version of redox_users with argon behind a feature
flag (enabled by default). There had been some buzz a while back about
the size of the dependency tree for this crate and `dirs` earlier, so
I've finally gotten around to doing my bit.
@soc
Copy link
Collaborator

soc commented Aug 27, 2020

There had been some buzz a while back about the size of the dependency tree for this crate and dirs earlier

Oh, interesting – do you have a link?

@soc soc merged commit e776c08 into dirs-dev:main Aug 27, 2020
@MggMuggins
Copy link
Contributor Author

Thanks! Here's the tracking issue for this: https://gitlab.redox-os.org/redox-os/users/-/issues/26

@soc
Copy link
Collaborator

soc commented Sep 5, 2020

Ah thanks!

Kinda weird that this crypto-bro-wearing-sunglasses-on-profile-pic linked in the Redox thread behaves exactly like one would expect from a crypto-bro-wearing-sunglasses-on-profile-pic. I think his behavior caught my attention multiple times already.

Maybe I should have kept dirs archived ...

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.

2 participants