We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
So that #318 can be merged but without being mentioned in the RFC which is supposed to describe parts of Matroska already in use.
The text was updated successfully, but these errors were encountered:
#425 would benefit from this as well.
Sorry, something went wrong.
We may need a different label to differentiate new v5 elements from new enum values as in #423.
(there is one)
the new label "build+system" is not readable, I don't want open a new issue.
reopened #445 not to pollute this discussion
No branches or pull requests
So that #318 can be merged but without being mentioned in the RFC which is supposed to describe parts of Matroska already in use.
The text was updated successfully, but these errors were encountered: