make wording around duplicate tracestate headers more precise #552
Conversation
This file contains 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
basti1302
added
Editorial
pellared
approved these changes
Nov 6, 2023
kalyanaj
approved these changes
Nov 14, 2023
jcopi
approved these changes
Nov 14, 2023
Participants must not add duplicated tracestate keys, but they are not responsible for cleaning up duplicated tracestate keys that another updstream participant has added. fixes w3c#548
basti1302
force-pushed
the
clarify-handling-of-duplicate-tracestate-keys-548
branch
from
662b959
to
7946bf2
Compare
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.
Participants must not add duplicated tracestate keys, but they are not responsible for cleaning up duplicated tracestate keys that another updstream participant has added.
fixes #548
Preview | Diff