-
Notifications
You must be signed in to change notification settings - Fork 169
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
Clarify spec for type #378
Labels
Comments
We also need to
|
johnmhoran
added a commit
that referenced
this issue
Jan 24, 2025
Reference: #378 Signed-off-by: John M. Horan <[email protected]>
johnmhoran
added a commit
that referenced
this issue
Jan 24, 2025
Reference: #378 Signed-off-by: John M. Horan <[email protected]>
johnmhoran
added a commit
that referenced
this issue
Jan 29, 2025
Reference: #378 Signed-off-by: John M. Horan [email protected]
johnmhoran
added a commit
that referenced
this issue
Jan 29, 2025
Reference: #378 Signed-off-by: John M. Horan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm beginning to work on the updates to
Relevant issues and PRs:
Clarifications, in particular about version encoding #35
Add RFC 2119/8174 note and convert terms to uppercase as needed #373
Add RFC 2119/8174 note and convert terms to uppercase as needed #373 (comment)
Add RFC 2119/8174 note and convert terms to uppercase as needed #373 (comment)
Add RFC 2119/8174 note and convert terms to uppercase as needed #373 (comment)
Clarify encoding of colon between scheme and type #361
The text was updated successfully, but these errors were encountered: