Skip to content
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 condition Cversion implicit range and bundle Cversion redefinition by components #281

Merged
merged 6 commits into from Jan 30, 2024

Conversation

jkrech
Copy link
Member

@jkrech jkrech commented Jan 29, 2024

Clarify that in conditions Cversion and Capiversion specified by minVersion only only resolve to true for compatible versions, meaning for the same major version value as specified in minVersion.
closing #273
closing #274

Clarify that in conditions Cversion and Capiversion specified by minVersion only only resolve to true for compatible versions, meaning for the same major version value as specified in minVersion.
clarifying that components within a bundle may define their own version.
Correct the bundle description. The bundle does not specify Cgroup and Cversion can be redefined by components within a bundle.
fix missing formatting.
@jkrech jkrech changed the title Update conditions_schema.txt Clarify condition Cversion implicit range and bundle Cversion redefinition by components Jan 29, 2024
@jkrech jkrech requested a review from brondani January 29, 2024 19:23
doxygen/src/components_schema.txt Outdated Show resolved Hide resolved
fixing typos

Co-authored-by: Daniel Brondani <daniel.brondani@arm.com>
@jkrech jkrech requested a review from brondani January 30, 2024 10:27
Copy link
Collaborator

@brondani brondani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants