GitHub user cwanda opened a pull request:
https://github.com/apache/incubator-mynewt-site/pull/155
MYNEWT-557 Document Override of Undefined Settings
MYNEWT-557 Document Override of Undefined Settings
Support was added to the 'newt build' command to print out an "ignoring
override of undefined settings" message whenlog level is set to DEBUG. Added
Override of Undefined System Configuration Setting section to explain this and
an explanation of why a BSP package overrides undefined settings.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cwanda/incubator-mynewt-site MYNEWT-557
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-mynewt-site/pull/155.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #155
----
commit f9e50056fc3b0a87b3ab67fcd03e230cb740dfb9
Author: cwanda <[email protected]>
Date: 2017-02-16T07:01:38Z
Update Event Queue OS Guide and Tutorial for new event queue implementation.
1) Updated Event Queue OS guide description, added description for
os_eventq_designate and os_eventq_run functions,
deleted os_eventq_dflt_set function.
2) Updated Event Queue tutorial to show how to use Mynewt default eventq
and to create dedicated event queue.
3) Modified the example to use the nRF52 board.
commit 9f3753e9c53f029a08cb2ae89908107af0e1dbd7
Author: cwanda <[email protected]>
Date: 2017-02-19T06:35:44Z
MYNEWT-557 Document Override of Undefined Settings
Support was added to the 'newt build' command to print out an "ignoring
override of undefined settings" message when
log level is set to DEBUG. Added Override of Undefined System Configuration
Setting section to explan this and also
added explanation of why a BSP package overrides undefined settings.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
