Open
Conversation
aparcar
force-pushed
the
develop
branch
2 times, most recently
from
e4b439f to
700c58c
Compare
Contributor
|
Can you document it before merging? |
Member
Author
|
@nicopace where should the documentation go to? I currently can't find any documentation about the options.conf file at all |
the new option compiles all packages as the given repo. This simplifies usage in a CLI system while still honoring libremesh.sdk.config.
Contributor
|
Yes, the README would be ok. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
the new option compiles all packages as the given repo. This simplifies
usage in a CLI system while still honoring libremesh.sdk.config.