configure: remove superfluous experimental warning for HTTP/3#21139
Closed
Fullmetal5 wants to merge 1 commit intocurl:masterfrom
Closed
configure: remove superfluous experimental warning for HTTP/3#21139Fullmetal5 wants to merge 1 commit intocurl:masterfrom
Fullmetal5 wants to merge 1 commit intocurl:masterfrom
Conversation
This warning was created at a time when all backends for HTTP/3 were experimental. Since there are now non-experimental backends this warning is incorrect in some cases and was already handled by backends that were added to the experimental list. Follow-up to 0535f6e
vszakats
approved these changes
Mar 28, 2026
bagder
approved these changes
Mar 28, 2026
Member
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This warning was created at a time when all backends for HTTP/3 were experimental. Since there are now non-experimental backends this warning is incorrect in some cases and was already handled by backends that were added to the experimental list.
Follow-up to 0535f6e