-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
LibCore: Support IPv6 for TCP and UDP connection #276
Conversation
a9d08e5
to
120981c
Compare
CI is failing unfortunately, does it build on your machine? |
yes |
Have you tried rebased onto the latest |
do I have to? It build successfully on my machine |
If it doesn't build on CI it likely won't build on other's machines, please do try, this is the error reported by CI
|
6502aa7
to
21dff27
Compare
I don't receive that errors, is it because the version of gcc? |
Have you rebased your local branch onto the latest master? |
Hello! One or more of the commit messages in this PR do not match the Ladybird code submission policy, please check the |
I said "rebase" not "merge" :( |
I will fix it later today |
fixed |
beda671
to
21dff27
Compare
814e6be
to
b9fa818
Compare
Do you guys need any help testing out features for this new browser?
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Andrew Kaster ***@***.***>
Sent: Friday, July 5, 2024 12:07:12 PM
To: LadybirdBrowser/ladybird ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [LadybirdBrowser/ladybird] LibCore: Support IPv6 for TCP and UDP connection (PR #276)
@ADKaster approved this pull request.
—
Reply to this email directly, view it on GitHub<#276 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BFWGZYLEGOV6AQR4VSMJICTZK3ADBAVCNFSM6AAAAABJ2UHCMOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCNRQHE4DEMRVHA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
This PR will add IPv6 support to Ladybird and give priority to IPv6 over IPv4
the PR still missing support of RFC 8305 and maybe we can add it as Phase 2