manifest: check in serialised manifest #121
Open
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
Responder platforms that do not support the generation of the `manifest.out.cbor` file at build time using the ruby `cbor-diag` gem, can use this as a pre-generated file that is checked in. For example, responders that use buildroot, where there is no feasible way to add support for `cbor-diag`. Signed-off-by: Wilfred Mallawa <[email protected]>
|
@alistair23 ping |
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.
Responder platforms that do not support the generation of the
manifest.out.cborfile at build time using the rubycbor-diaggem, can use this as a pre-generated file that is checked in.For example, responders that use buildroot, where there is no feasible way to add support for
cbor-diag.