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

deps: bump libc from 0.2.153 to 0.2.155 #2188

Merged
merged 1 commit into from
May 28, 2024
Merged

Conversation

huajingyun01
Copy link
Contributor

@codecov-commenter
Copy link

codecov-commenter commented May 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 42.53%. Comparing base (0cc0c62) to head (667da07).
Report is 44 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #2188       +/-   ##
===========================================
+ Coverage   30.91%   42.53%   +11.62%     
===========================================
  Files          53       53               
  Lines       20112    20324      +212     
  Branches     9755     9684       -71     
===========================================
+ Hits         6217     8645     +2428     
- Misses       7922     7974       +52     
+ Partials     5973     3705     -2268     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@sylvestre
Copy link
Collaborator

@huajingyun01 is there a something that you need in libc 0.2.155 ? thanks

@huajingyun01
Copy link
Contributor Author

@huajingyun01 is there a something that you need in libc 0.2.155 ? thanks

Hi @sylvestre I had to update libc to 0.2.155 to support LoongArch64, because sccache compilation based on musl LoongArch64 failed.
rust-lang/libc#3606

Thanks.

@riquito
Copy link

riquito commented May 28, 2024

Hi, I received the same PR for my project tuc riquito/tuc#151 and I just closed it because @huajingyun01 is forking multiple repositories and creating the same PRs over multiple repositories, for no clear reason

@sylvestre
Copy link
Collaborator

@riquito probably because Loongson has been paying developers to support the FLOSS ecosystem on this arch.
I have seen this happening in Debian too. It is legit stuff.

@huajingyun01 You might want to make it clear in your PR requests in general ;)

@sylvestre sylvestre merged commit 808e8fb into mozilla:main May 28, 2024
53 checks passed
@huajingyun01
Copy link
Contributor Author

@riquito probably because Loongson has been paying developers to support the FLOSS ecosystem on this arch. I have seen this happening in Debian too. It is legit stuff.

@huajingyun01 You might want to make it clear in your PR requests in general ;)

@sylvestre Thanks.

I really should take the time to provide a more detailed explanation for each PR as to why I need to make such a change.

Since there are too many repositories, I used the same comment, which didn't seem sincere, sorry I overlooked that.

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.

4 participants