mynewt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ad...@apache.org
Subject [2/2] incubator-mynewt-site git commit: Fixed broken links in install instructions for linux
Date Mon, 08 May 2017 19:01:03 GMT
Fixed broken links in install instructions for linux


Project: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/commit/02116bd4
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/02116bd4
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/02116bd4

Branch: refs/heads/asf-site
Commit: 02116bd4b871cd408e4af7d4f3ed6358f3026647
Parents: ea2670d
Author: aditihilbert <aditi@runtime.io>
Authored: Mon May 8 12:00:50 2017 -0700
Committer: aditihilbert <aditi@runtime.io>
Committed: Mon May 8 12:00:50 2017 -0700

----------------------------------------------------------------------
 develop/faq/answers/index.html                  | 50 ++------------------
 develop/mkdocs/search_index.json                | 17 ++++---
 develop/newt/install/newt_linux/index.html      |  8 ++--
 develop/newtmgr/install_linux/index.html        |  8 ++--
 .../get_started/native_install_intro/index.html |  2 +-
 .../os/tutorials/blinky_stm32f4disc/index.html  |  2 +-
 develop/os/tutorials/rbnano2/index.html         |  2 +-
 develop/sitemap.xml                             | 26 +++++-----
 latest/faq/answers/index.html                   | 50 ++------------------
 latest/mkdocs/search_index.json                 | 17 ++++---
 latest/newt/install/newt_linux/index.html       |  8 ++--
 latest/newtmgr/install_linux/index.html         |  8 ++--
 .../get_started/native_install_intro/index.html |  2 +-
 .../os/tutorials/blinky_stm32f4disc/index.html  |  2 +-
 latest/os/tutorials/rbnano2/index.html          |  2 +-
 latest/sitemap.xml                              | 26 +++++-----
 sitemap.xml                                     | 26 +++++-----
 v0_9_0/sitemap.xml                              | 26 +++++-----
 18 files changed, 104 insertions(+), 178 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/02116bd4/develop/faq/answers/index.html
----------------------------------------------------------------------
diff --git a/develop/faq/answers/index.html b/develop/faq/answers/index.html
index 0a4eb7b..6385c7f 100644
--- a/develop/faq/answers/index.html
+++ b/develop/faq/answers/index.html
@@ -276,52 +276,10 @@
 <h3 id="i-am-not-on-the-committer-list-how-do-i-submit-a-patch">I am not on the committer list. How do I submit a patch?</h3>
 <p><br></p>
 <p><strong>You submit your proposed changes for your peers with committer status to review and merge.</strong></p>
-<p>The "develop" branch on Mynewt's repository contains the most recent changes made by the community of developers. Contributions from you need to go into this branch. The essential steps to setting up your project space for working with the latest code from "develop" and make pull requests into "develop" to get your code added are the following:</p>
-<p><strong>Step 1:</strong> Create a fork of the entire Mynewt repository on github.com.</p>
-<p><strong>Step 2:</strong> Setup repository on your laptop to use code in “develop” branch. You then create a new branch “mybranch” using “git checkout –b”. You also add a remote handle named “fork” that points to the github fork you created in Step 1.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">    $ newt new devproject
-    $ cd devproject
-    $ vi project.yml
-        # change version to 0-dev for repository.apache-mynewt-core
-    $ newt install
-    $ cd repos/apache-mynewt-core
-    $ git status
-        On branch develop
-        Your branch is up-to-date with &#39;origin/develop&#39;.
-        nothing to commit, working directory clean
-    $ git checkout –b mybranch
-    $ git remote -v
-        origin https://github.com/apache/incubator-mynewt-core.git (fetch) 
-        origin https://github.com/apache/incubator-mynewt-core.git (push)
-    $ git remote add fork https://github.com/&lt;user&gt;/incubator-mynewt-core 
-    $ git remote -v
-        origin https://github.com/apache/incubator-mynewt-core.git (fetch) 
-        origin https://github.com/apache/incubator-mynewt-core.git (push)
-        fork https://github.com/&lt;user&gt;/incubator-mynewt-core (fetch) 
-        fork https://github.com/&lt;user&gt;/incubator-mynewt-core (push)
-</pre></div>
-
-
-<p><strong>Step 3:</strong> Check you are in “mybranch”. Write code. Stage and commit your changes
-(example shows adding all).</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">   $ git checkout mybranch
-   $ git add .
-   $ git commit –m “your message about your code changes”
-</pre></div>
-
-
-<p><strong>Step 4:</strong> Always pull the latest from develop on Apache mirror to “mybranch” before pushing any changes to remotes. If you see merge conflicts, resolve them first.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">   $ git pull --rebase origin develop
-</pre></div>
-
-
-<p><strong>Step 5:</strong> Push your changes to “mybranch” branch on your github fork. If “mybranch” does not exist yet on your github fork, the command automa;cally creates it.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">   $ git push fork mybranch
-</pre></div>
-
-
-<p><strong>Step 6:</strong> Generate a pull request from “mybranch” in your fork to “develop” in Mynewt using the "New pull request" button on github.com.</p>
-<p><img alt="Mynewt Dev Cycle" src="../mynewt_dev_cycle.jpg" /></p>
+<p>The process to submit a Pull Request on github.com is described on the <a href="https://cwiki.apache.org/confluence/display/MYNEWT/Submitting+Pull+Requests">Confluence page for the project</a>. </p>
+<h3 id="i-am-a-committer-in-the-project-can-i-merge-my-own-pull-request-into-the-git-repository">I am a committer in the project. Can I merge my own Pull Request into the git repository?</h3>
+<p>Yes, but only if your Pull Request has been reviewed and approved by another committer in Apache Mynewt.
+The process to merge a Pull Request is described on the <a href="https://cwiki.apache.org/confluence/display/MYNEWT/Merging+Pull+Requests">Confluence page for the project</a>.</p>
 <h3 id="i-would-like-to-make-some-edits-to-the-documentation-what-do-i-do">I would like to make some edits to the documentation. What do I do?</h3>
 <p><br></p>
 <p>You submit your proposed changes for your peers with committer status to review and merge. </p>

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/02116bd4/develop/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/develop/mkdocs/search_index.json b/develop/mkdocs/search_index.json
index 808a034..7090d01 100644
--- a/develop/mkdocs/search_index.json
+++ b/develop/mkdocs/search_index.json
@@ -187,7 +187,7 @@
         }, 
         {
             "location": "/newt/install/newt_linux/", 
-            "text": "Installing Newt on Linux\n\n\nYou can install the latest stable release (1.0.0) of the newt tool from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:\n\n\n\n\nSet up your computer to retrieve Debian packages from the runtimeco debian package repository.\n\n\nInstall the latest stable release version of newt from a Debian binary package. \n\n\nInstall the latest stable release version of newt from a Debian source package.\n\n\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n See \nSetting Up an Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to:  \n\n\n\n\nUse the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newt tool. \n\n\n\n\n\n\nSetting Up Your Computer to Get Packages from runtimeco\n\n\nThe new
 t Debian packages are stored in a private repository on \nhttps://github/runtimeco/debian-mynewt\n.  The following steps must be performed on your computer to retreive packages from the repository:\n\n\nNote:\n You only need to perform this setup once on your computer.\n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco debian repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nInstall the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo (\nNote:\n There is  a \n-\n after  \napt-key add\n):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the \nmynewt.list\
 n apt source list file.\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF\nroot$exit\n\n\n\n\n\nNote:\n Do not forget to exit the root shell.\n\n\n\nVerify the content of the source list file:\n\n\n$more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\n\n\n\n\n\n \n\n\nInstalling the Latest Release of Newt from a Binary Package\n\n\nFor Linux amd64 platforms, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:\n\n\n$sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree       \nReading state information... Done\n\n
       ...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...\n\n\n\n\n\n\nSee \nChecking the Installed Version of Newt\n to verify that you are using the installed version of newt.\n\n\n\n\nInstalling the Latest Stable Release of Newt from a Source Package\n\n\nIf you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install.\n\n\nNote\n: Newt version 1.0.0 has been tested on Linux amd64 platforms. Version 1.0.0 does not build on 32 bit platforms but have been fixed for the next release.\n\n\n\n\nInstalling Go 1.7\n\n\nYou need Go version 1.7 or higher to build Newt version 1.0.0.  Currently, the latest Go version that Ubuntu installs is 1.6.  Run \ngo version\n to check if you have Go 1.7 installed. \n\n\n\n\nInstall Go vers
 ion 1.7:\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n     ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\nYou can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\nInstalling from the Source Package\n\n\nCreate a directory and change into the directory, download the source package, and build a binary package from the source package:\n\n\nmkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for \nuser\n: \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/deb
 ian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\ndpkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n           ...\n\ndpkg-deb: building package \nnewt\n in \n../newt_1.0.0-1_amd64.deb\n.\n dpkg-genchanges --build=any,all \n../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can\nt drop privileges for downloading as file \nnewt_1.0.0-1.dsc\n couldn\nt be accessed by user \n_apt\n. - pkgAcquire::Run (13: Permission denied)\n\n\n\n\n\nNote:\n You can ignore the \"Permission denied\" warning message at the end of the command.\n\n\n\nInstall the newt binary package that is created from the source pack
 age:\n\n\nNote:\n The file name for the binary package has the format: newt_1.0.0-1_\narch\n.deb,  where \narch\n is a value that identifies your host architecture.  \n\n\n$sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Reading database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...\n\n\n\n\n\n\n\n Checking the Installed Version of Newt\n\n\nAfter you have installed newt from either a Debian binary or source package, check that you are using the installed version of newt from \n/usr/bin\n. \n\n\nCheck the modification time of the binary and the newt tool that you are using:\n\n\n$ls -l /usr/bin/newt\n-rwxr-xr-x 1 root root 6919280 Apr 22 10:09 /usr/bin/newt\n$which newt\n/usr/bin/newt\n$newt version\nApache Newt (incubating) version: 1.0.0\n\n\n\n\n\nNote:\n If you previously built newt from source and the output of \nwhich newt\
 n shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/bin\" for your PATH environment variable and export it. \n\n\n\nGet information about newt:\n\n\n$newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating system. Newt provides both build and package management in a single\ntool, which allows you to compose an embedded application, and set of\nprojects, and then build the necessary artifacts from those projects. For more\ninformation on the Mynewt operating system, please visit\nhttps://mynewt.apache.org/.\n\nPlease use the newt help command, and specify the name of the command you want\nhelp for, for help on how to use a specific command\n\nUsage:\n  newt [flags]\n  newt [command]\n\nExamples:\n  newt\n  newt help [\ncommand-name\n]\n    For help on \ncommand-name\n.  If not specified, print this message.\n\nAvailable Commands:\n  build        Build one or more targets\n  clean        Delete build artifacts for one o
 r more targets\n  create-image Add image header to target binary\n  debug        Open debugger session to target\n  info         Show project info\n  install      Install project dependencies\n  load         Load built target to board\n  mfg          Manufacturing flash image commands\n  new          Create a new project\n  pkg          Create and manage packages in the current workspace\n  run          build/create-image/download/debug \ntarget\n\n  size         Size of target components\n  sync         Synchronize project dependencies\n  target       Commands to create, delete, configure, and query targets\n  test         Executes unit tests for one or more packages\n  upgrade      Upgrade project dependencies\n  vals         Display valid values for the specified element type(s)\n  version      Display the Newt version number\n\nFlags:\n  -h, --help              Help for newt commands\n  -j, --jobs int          Number of concurrent build jobs (default 8)\n  -l, --loglevel string 
   Log level (default \nWARN\n)\n  -o, --outfile string    Filename to tee output to\n  -q, --quiet             Be quiet; only display error output\n  -s, --silent            Be silent; don\nt output anything\n  -v, --verbose           Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.", 
+            "text": "Installing Newt on Linux\n\n\nYou can install the latest stable release (1.0.0) of the newt tool from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:\n\n\n\n\nSet up your computer to retrieve Debian packages from the runtimeco debian package repository.\n\n\nInstall the latest stable release version of newt from a Debian binary package. \n\n\nInstall the latest stable release version of newt from a Debian source package.\n\n\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n See \nSetting Up an Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to:  \n\n\n\n\nUse the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newt tool. \n\n\n\n\n\n\nSetting Up Your Computer to Get Packages from runtimeco\n\n\nThe new
 t Debian packages are stored in a private repository on \nhttps://github/runtimeco/debian-mynewt\n.  The following steps must be performed on your computer to retreive packages from the repository:\n\n\nNote:\n You only need to perform this setup once on your computer.\n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco debian repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nInstall the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo (\nNote:\n There is  a \n-\n after  \napt-key add\n):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the \nmynewt.list\
 n apt source list file.\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\nroot$exit\n\n\n\n\n\nNote:\n Do not forget to exit the root shell.\n\n\n\nVerify the content of the source list file:\n\n\n$more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\n\n\n\n\n\n \n\n\nInstalling the Latest Release of Newt from a Binary Package\n\n\nFor Linux amd64 platforms, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:\n\n\n$sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree       \nReading state information... Done\n\n    
   ...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...\n\n\n\n\n\n\nSee \nChecking the Installed Version of Newt\n to verify that you are using the installed version of newt.\n\n\n\n\nInstalling the Latest Stable Release of Newt from a Source Package\n\n\nIf you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install.\n\n\nNote\n: Newt version 1.0.0 has been tested on Linux amd64 platforms. Version 1.0.0 does not build on 32 bit platforms but have been fixed for the next release.\n\n\n\n\nInstalling Go 1.7\n\n\nYou need Go version 1.7 or higher to build Newt version 1.0.0.  Currently, the latest Go version that Ubuntu installs is 1.6.  Run \ngo version\n to check if you have Go 1.7 installed. \n\n\n\n\nInstall Go version 
 1.7:\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n     ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\nYou can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\nInstalling from the Source Package\n\n\nCreate a directory and change into the directory, download the source package, and build a binary package from the source package:\n\n\nmkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for \nuser\n: \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/debian-
 mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\ndpkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n           ...\n\ndpkg-deb: building package \nnewt\n in \n../newt_1.0.0-1_amd64.deb\n.\n dpkg-genchanges --build=any,all \n../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can\nt drop privileges for downloading as file \nnewt_1.0.0-1.dsc\n couldn\nt be accessed by user \n_apt\n. - pkgAcquire::Run (13: Permission denied)\n\n\n\n\n\nNote:\n You can ignore the \"Permission denied\" warning message at the end of the command.\n\n\n\nInstall the newt binary package that is created from the source package:
 \n\n\nNote:\n The file name for the binary package has the format: newt_1.0.0-1_\narch\n.deb,  where \narch\n is a value that identifies your host architecture.  \n\n\n$sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Reading database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...\n\n\n\n\n\n\n\n Checking the Installed Version of Newt\n\n\nAfter you have installed newt from either a Debian binary or source package, check that you are using the installed version of newt from \n/usr/bin\n. \n\n\nCheck the modification time of the binary and the newt tool that you are using:\n\n\n$ls -l /usr/bin/newt\n-rwxr-xr-x 1 root root 6919280 Apr 22 10:09 /usr/bin/newt\n$which newt\n/usr/bin/newt\n$newt version\nApache Newt (incubating) version: 1.0.0\n\n\n\n\n\nNote:\n If you previously built newt from source and the output of \nwhich newt\n sh
 ows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/bin\" for your PATH environment variable and export it. \n\n\n\nGet information about newt:\n\n\n$newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating system. Newt provides both build and package management in a single\ntool, which allows you to compose an embedded application, and set of\nprojects, and then build the necessary artifacts from those projects. For more\ninformation on the Mynewt operating system, please visit\nhttps://mynewt.apache.org/.\n\nPlease use the newt help command, and specify the name of the command you want\nhelp for, for help on how to use a specific command\n\nUsage:\n  newt [flags]\n  newt [command]\n\nExamples:\n  newt\n  newt help [\ncommand-name\n]\n    For help on \ncommand-name\n.  If not specified, print this message.\n\nAvailable Commands:\n  build        Build one or more targets\n  clean        Delete build artifacts for one or mo
 re targets\n  create-image Add image header to target binary\n  debug        Open debugger session to target\n  info         Show project info\n  install      Install project dependencies\n  load         Load built target to board\n  mfg          Manufacturing flash image commands\n  new          Create a new project\n  pkg          Create and manage packages in the current workspace\n  run          build/create-image/download/debug \ntarget\n\n  size         Size of target components\n  sync         Synchronize project dependencies\n  target       Commands to create, delete, configure, and query targets\n  test         Executes unit tests for one or more packages\n  upgrade      Upgrade project dependencies\n  vals         Display valid values for the specified element type(s)\n  version      Display the Newt version number\n\nFlags:\n  -h, --help              Help for newt commands\n  -j, --jobs int          Number of concurrent build jobs (default 8)\n  -l, --loglevel string   Lo
 g level (default \nWARN\n)\n  -o, --outfile string    Filename to tee output to\n  -q, --quiet             Be quiet; only display error output\n  -s, --silent            Be silent; don\nt output anything\n  -v, --verbose           Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.", 
             "title": "Install Newt on Linux"
         }, 
         {
@@ -197,7 +197,7 @@
         }, 
         {
             "location": "/newt/install/newt_linux/#setting-up-your-computer-to-get-packages-from-runtimeco", 
-            "text": "The newt Debian packages are stored in a private repository on  https://github/runtimeco/debian-mynewt .  The following steps must be performed on your computer to retreive packages from the repository:  Note:  You only need to perform this setup once on your computer.   Install the  apt-transport-https  package to use HTTPS to retrieve packages.   Download the public key for the runtimeco debian repository and import the key into the apt keychain.  Add the repository for the binary and source packages to the apt source list.   \nInstall the apt-transport-https package:  $sudo apt-get update\n$sudo apt-get install apt-transport-https   Download the public key for the runtimeco apt repo ( Note:  There is  a  -  after   apt-key add ):  wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -   Add the repository for the binary and source packages to the  mynewt.list  apt source list file.  $sudo -s\n[sudo] pas
 sword for  user :\nroot$ cat   /etc/apt/sources.list.d/mynewt.list  EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF\nroot$exit  Note:  Do not forget to exit the root shell.  \nVerify the content of the source list file:  $more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main", 
+            "text": "The newt Debian packages are stored in a private repository on  https://github/runtimeco/debian-mynewt .  The following steps must be performed on your computer to retreive packages from the repository:  Note:  You only need to perform this setup once on your computer.   Install the  apt-transport-https  package to use HTTPS to retrieve packages.   Download the public key for the runtimeco debian repository and import the key into the apt keychain.  Add the repository for the binary and source packages to the apt source list.   \nInstall the apt-transport-https package:  $sudo apt-get update\n$sudo apt-get install apt-transport-https   Download the public key for the runtimeco apt repo ( Note:  There is  a  -  after   apt-key add ):  wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -   Add the repository for the binary and source packages to the  mynewt.list  apt source list file.  $sudo -s\n[sudo] pas
 sword for  user :\nroot$ cat   /etc/apt/sources.list.d/mynewt.list  EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\nroot$exit  Note:  Do not forget to exit the root shell.  \nVerify the content of the source list file:  $more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main", 
             "title": "Setting Up Your Computer to Get Packages from runtimeco"
         }, 
         {
@@ -11832,7 +11832,7 @@
         }, 
         {
             "location": "/newtmgr/install_linux/", 
-            "text": "Installing Newtmgr on Linux\n\n\nYou can install the latest stable release (1.0.0) of the newtmgr tool from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:\n\n\n\n\n\n\nSet up your computer to retrieve Debian packages from the runtimeco debian package repository. \n\n\nNote:\n You can skip this step if you already set up your computer to access the runtimeco debian repository when you installed the newt tool. \n\n\n\n\n\n\nInstall the latest stable release version of newtmgr from a Debian binary package. \n\n\n\n\nInstall the latest stable release version of newtmgr from a Debian source package.\n\n\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n See \nSetting Up an Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to:  \n\n\n\n\nUse the newtmgr tool with the latest updates from the master branch. The master branch may be unstable 
 and we recommend that you use the latest stable release version.\n\n\nContribute to the newtmgr tool. \n\n\n\n\n\n\nSetting Up Your Computer to Get Packages from runtimeco\n\n\nThe newtmgr Debian packages are stored in a private repository on \nhttps://github/runtimeco/debian-mynewt\n.   You must set up the following on your computer to retreive packages from the repository:\n\n\nNote\n: You only need to perform this setup once on your computer and you may have already done so when you installed the newt tool. \n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco debian repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nInstall the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo  (\nNote:\n Th
 ere is  a \n-\n after  \napt-key add\n):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the \nmynewt.list\n apt source list file.\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF\nroot$exit\n\n\n\n\n\nNote:\n Do not forget to exit the root shell.\n\n\n\nVerify the content of the source list file:\n\n\n$more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\n\n\n\n\n\n \n\n\nInstalling the Latest Release of Newtmgr from a Binary Package\n\n\nFor Linux amd64 platforms, 
 you can install the latest stable version (1.0.0) of newtmgr from the newtmgr Debian binary package:\n\n\n$sudo apt-get update\n$sudo apt-get install newtmgr\nReading package lists... Done\nBuilding dependency tree       \nReading state information... Done\nThe following NEW packages will be installed:\n  newtmgr\n0 upgraded, 1 newly installed, 0 to remove and 204 not upgraded.\nNeed to get 0 B/2,312 kB of archives.\nAfter this operation, 11.5 MB of additional disk space will be used.\nSelecting previously unselected package newtmgr.\n(Reading database ... 211647 files and directories currently installed.)\nPreparing to unpack .../newtmgr_1.0.0-1_amd64.deb ...\nUnpacking newtmgr (1.0.0-1) ...\nSetting up newtmgr (1.0.0-1) \n\n\n\n\n\n\nSee \nChecking the Installed Version of Newtmgr\n to verify that you are using the installed version of newtmgr.\n\n\n\n\nInstalling the Latest Stable Release of Newtmgr from a Source Package\n\n\nIf you are running Linux on a different architecture, 
 you can install the Debian source package for the latest stable release (1.0.0) of newtmgr. The installation of the source package builds the newtmgr binary and creates a Debian binary package that you then install.\n\n\nNote\n: Newtmgr version 1.0.0 has been tested on Linux amd64 platforms. \n\n\n\n\nInstalling Go 1.7\n\n\nYou need Go version 1.7 or higher to build Newtmgr version 1.0.0.  Currently, the latest Go version that Ubuntu installs is 1.6.  Run \ngo version\n to check if you have Go 1.7 installed. \n\n\n\n\nInstall Go version 1.7:\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n     ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\nYou can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\nInstalling from the Source Package\n\n\nCreate a directory and change into the directory, d
 ownload the source package, and build a binary package from the source package:\n\n\nmkdir newtmgr_source\n$cd newtmgr_source\n$sudo apt-get --build source newtmgr\n[sudo] password for \nuser\n: \n\nsudo apt-get --build source newtmgr\nReading package lists... Done\nNeed to get 1,867 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (dsc) [822 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (diff) [2,372 B]\nFetched 1,867 kB in 1s (1,767 kB/s) \n\n           ...\n\ndpkg-deb: building package \nnewtmgr\n in \n../newtmgr_1.0.0-1_amd64.deb\n.\n dpkg-genchanges --build=any,all \n../newtmgr_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newtmgr-1.0.0\ndpkg-buildpackage: info: 
 binary-only upload (no source included)\nW: Can\nt drop privileges for downloading as file \nnewtmgr_1.0.0-1.dsc\n couldn\nt be accessed by user \n_apt\n. - pkgAcquire::Run (13: Permission denied)\n\n\n\n\n\nNote:\n You can ignore the \"Permission denied\" warning message at the end of the command.\n\n\n\nInstall the newtmgr binary package that is created from the source package:\n\n\nNote:\n The file name for the binary package has the format: newtmgr_1.0.0-1_\narch\n.deb,  where \narch\n is a value that identifies your host architecture.\n\n\n$sudo dpkg -i newtmgr_1.0.0-1_amd64.deb \nSelecting previously unselected package newtmgr.\n(Reading database ... 215099 files and directories currently installed.)\nPreparing to unpack newtmgr_1.0.0-1_amd64.deb ...\nUnpacking newtmgr (1.0.0-1) ...\nSetting up newtmgr (1.0.0-1) ...\n\n\n\n\n\n\n\n Checking the Installed Version of Newtmgr\n\n\nAfter you have installed newtmgr from either a Debian binary or source package, check that you are u
 sing the installed version of newtmgr from \n/usr/bin\n. \n\n\nCheck the modification time of the binary and the newtmgr tool that you are using:\n\n\n$ls -l /usr/bin/newtmgr\n-rwxr-xr-x 1 root root 11473328 Apr 25 10:10 /usr/bin/newtmgr\n$which newtmgr\n/usr/bin/newtmgr\n\n\n\n\n\nNote:\n If you previously built newtmgr from source and the output of \nwhich newtmgr\n shows \"$GOPATH/bin/newtmgr\", you will need to move \"$GOPATH/bin\" after \"/usr/bin\" for your PATH environment variable and export it.\n\n\n\nGet information about newtmgr:\n\n\n$newtmgr\nNewtmgr helps you manage remote devices running the Mynewt OS\n\nUsage:\n  newtmgr [flags]\n  newtmgr [command]\n\nAvailable Commands:\n  config      Read or write a config value on a device\n  conn        Manage newtmgr connection profiles\n  crash       Send a crash command to a device\n  datetime    Manage datetime on a device\n  echo        Send data to a device and display the echoed back data\n  fs          Access files on a 
 device\n  image       Manage images on a device\n  log         Manage logs on a device\n  mpstats     Read memory pool statistics from a device\n  reset       Send reset request to a device\n  run         Run test procedures on a device\n  stat        Read statistics from a device\n  taskstats   Read task statistics from a device\n\nFlags:\n  -c, --conn string       connection profile to use\n  -h, --help              Help for newtmgr commands\n  -l, --loglevel string   log level to use (default \ninfo\n)\n  -t, --trace             print all bytes transmitted and received\n\nUse \nnewtmgr [command] --help\n for more information about a command.\n\n\n\n\n\n```", 
+            "text": "Installing Newtmgr on Linux\n\n\nYou can install the latest stable release (1.0.0) of the newtmgr tool from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:\n\n\n\n\n\n\nSet up your computer to retrieve Debian packages from the runtimeco debian package repository. \n\n\nNote:\n You can skip this step if you already set up your computer to access the runtimeco debian repository when you installed the newt tool. \n\n\n\n\n\n\nInstall the latest stable release version of newtmgr from a Debian binary package. \n\n\n\n\nInstall the latest stable release version of newtmgr from a Debian source package.\n\n\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n See \nSetting Up an Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to:  \n\n\n\n\nUse the newtmgr tool with the latest updates from the master branch. The master branch may be unstable 
 and we recommend that you use the latest stable release version.\n\n\nContribute to the newtmgr tool. \n\n\n\n\n\n\nSetting Up Your Computer to Get Packages from runtimeco\n\n\nThe newtmgr Debian packages are stored in a private repository on \nhttps://github/runtimeco/debian-mynewt\n.   You must set up the following on your computer to retreive packages from the repository:\n\n\nNote\n: You only need to perform this setup once on your computer and you may have already done so when you installed the newt tool. \n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco debian repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nInstall the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo  (\nNote:\n Th
 ere is  a \n-\n after  \napt-key add\n):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the \nmynewt.list\n apt source list file.\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\nroot$exit\n\n\n\n\n\nNote:\n Do not forget to exit the root shell.\n\n\n\nVerify the content of the source list file:\n\n\n$more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\n\n\n\n\n\n \n\n\nInstalling the Latest Release of Newtmgr from a Binary Package\n\n\nFor Linux amd64 platforms, you 
 can install the latest stable version (1.0.0) of newtmgr from the newtmgr Debian binary package:\n\n\n$sudo apt-get update\n$sudo apt-get install newtmgr\nReading package lists... Done\nBuilding dependency tree       \nReading state information... Done\nThe following NEW packages will be installed:\n  newtmgr\n0 upgraded, 1 newly installed, 0 to remove and 204 not upgraded.\nNeed to get 0 B/2,312 kB of archives.\nAfter this operation, 11.5 MB of additional disk space will be used.\nSelecting previously unselected package newtmgr.\n(Reading database ... 211647 files and directories currently installed.)\nPreparing to unpack .../newtmgr_1.0.0-1_amd64.deb ...\nUnpacking newtmgr (1.0.0-1) ...\nSetting up newtmgr (1.0.0-1) \n\n\n\n\n\n\nSee \nChecking the Installed Version of Newtmgr\n to verify that you are using the installed version of newtmgr.\n\n\n\n\nInstalling the Latest Stable Release of Newtmgr from a Source Package\n\n\nIf you are running Linux on a different architecture, you 
 can install the Debian source package for the latest stable release (1.0.0) of newtmgr. The installation of the source package builds the newtmgr binary and creates a Debian binary package that you then install.\n\n\nNote\n: Newtmgr version 1.0.0 has been tested on Linux amd64 platforms. \n\n\n\n\nInstalling Go 1.7\n\n\nYou need Go version 1.7 or higher to build Newtmgr version 1.0.0.  Currently, the latest Go version that Ubuntu installs is 1.6.  Run \ngo version\n to check if you have Go 1.7 installed. \n\n\n\n\nInstall Go version 1.7:\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n     ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\nYou can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\nInstalling from the Source Package\n\n\nCreate a directory and change into the directory, downl
 oad the source package, and build a binary package from the source package:\n\n\nmkdir newtmgr_source\n$cd newtmgr_source\n$sudo apt-get --build source newtmgr\n[sudo] password for \nuser\n: \n\nsudo apt-get --build source newtmgr\nReading package lists... Done\nNeed to get 1,867 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (dsc) [822 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (diff) [2,372 B]\nFetched 1,867 kB in 1s (1,767 kB/s) \n\n           ...\n\ndpkg-deb: building package \nnewtmgr\n in \n../newtmgr_1.0.0-1_amd64.deb\n.\n dpkg-genchanges --build=any,all \n../newtmgr_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newtmgr-1.0.0\ndpkg-buildpackage: info: bina
 ry-only upload (no source included)\nW: Can\nt drop privileges for downloading as file \nnewtmgr_1.0.0-1.dsc\n couldn\nt be accessed by user \n_apt\n. - pkgAcquire::Run (13: Permission denied)\n\n\n\n\n\nNote:\n You can ignore the \"Permission denied\" warning message at the end of the command.\n\n\n\nInstall the newtmgr binary package that is created from the source package:\n\n\nNote:\n The file name for the binary package has the format: newtmgr_1.0.0-1_\narch\n.deb,  where \narch\n is a value that identifies your host architecture.\n\n\n$sudo dpkg -i newtmgr_1.0.0-1_amd64.deb \nSelecting previously unselected package newtmgr.\n(Reading database ... 215099 files and directories currently installed.)\nPreparing to unpack newtmgr_1.0.0-1_amd64.deb ...\nUnpacking newtmgr (1.0.0-1) ...\nSetting up newtmgr (1.0.0-1) ...\n\n\n\n\n\n\n\n Checking the Installed Version of Newtmgr\n\n\nAfter you have installed newtmgr from either a Debian binary or source package, check that you are using
  the installed version of newtmgr from \n/usr/bin\n. \n\n\nCheck the modification time of the binary and the newtmgr tool that you are using:\n\n\n$ls -l /usr/bin/newtmgr\n-rwxr-xr-x 1 root root 11473328 Apr 25 10:10 /usr/bin/newtmgr\n$which newtmgr\n/usr/bin/newtmgr\n\n\n\n\n\nNote:\n If you previously built newtmgr from source and the output of \nwhich newtmgr\n shows \"$GOPATH/bin/newtmgr\", you will need to move \"$GOPATH/bin\" after \"/usr/bin\" for your PATH environment variable and export it.\n\n\n\nGet information about newtmgr:\n\n\n$newtmgr\nNewtmgr helps you manage remote devices running the Mynewt OS\n\nUsage:\n  newtmgr [flags]\n  newtmgr [command]\n\nAvailable Commands:\n  config      Read or write a config value on a device\n  conn        Manage newtmgr connection profiles\n  crash       Send a crash command to a device\n  datetime    Manage datetime on a device\n  echo        Send data to a device and display the echoed back data\n  fs          Access files on a devi
 ce\n  image       Manage images on a device\n  log         Manage logs on a device\n  mpstats     Read memory pool statistics from a device\n  reset       Send reset request to a device\n  run         Run test procedures on a device\n  stat        Read statistics from a device\n  taskstats   Read task statistics from a device\n\nFlags:\n  -c, --conn string       connection profile to use\n  -h, --help              Help for newtmgr commands\n  -l, --loglevel string   log level to use (default \ninfo\n)\n  -t, --trace             print all bytes transmitted and received\n\nUse \nnewtmgr [command] --help\n for more information about a command.\n\n\n\n\n\n```", 
             "title": "Install Newtmgr On Linux"
         }, 
         {
@@ -11842,7 +11842,7 @@
         }, 
         {
             "location": "/newtmgr/install_linux/#setting-up-your-computer-to-get-packages-from-runtimeco", 
-            "text": "The newtmgr Debian packages are stored in a private repository on  https://github/runtimeco/debian-mynewt .   You must set up the following on your computer to retreive packages from the repository:  Note : You only need to perform this setup once on your computer and you may have already done so when you installed the newt tool.    Install the  apt-transport-https  package to use HTTPS to retrieve packages.   Download the public key for the runtimeco debian repository and import the key into the apt keychain.  Add the repository for the binary and source packages to the apt source list.   \nInstall the apt-transport-https package:  $sudo apt-get update\n$sudo apt-get install apt-transport-https   Download the public key for the runtimeco apt repo  ( Note:  There is  a  -  after   apt-key add ):  wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -   Add the repository for the binary and source packages 
 to the  mynewt.list  apt source list file.  $sudo -s\n[sudo] password for  user :\nroot$ cat   /etc/apt/sources.list.d/mynewt.list  EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF\nroot$exit  Note:  Do not forget to exit the root shell.  \nVerify the content of the source list file:  $more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main", 
+            "text": "The newtmgr Debian packages are stored in a private repository on  https://github/runtimeco/debian-mynewt .   You must set up the following on your computer to retreive packages from the repository:  Note : You only need to perform this setup once on your computer and you may have already done so when you installed the newt tool.    Install the  apt-transport-https  package to use HTTPS to retrieve packages.   Download the public key for the runtimeco debian repository and import the key into the apt keychain.  Add the repository for the binary and source packages to the apt source list.   \nInstall the apt-transport-https package:  $sudo apt-get update\n$sudo apt-get install apt-transport-https   Download the public key for the runtimeco apt repo  ( Note:  There is  a  -  after   apt-key add ):  wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -   Add the repository for the binary and source packages 
 to the  mynewt.list  apt source list file.  $sudo -s\n[sudo] password for  user :\nroot$ cat   /etc/apt/sources.list.d/mynewt.list  EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\nEOF\nroot$exit  Note:  Do not forget to exit the root shell.  \nVerify the content of the source list file:  $more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main", 
             "title": "Setting Up Your Computer to Get Packages from runtimeco"
         }, 
         {
@@ -11957,7 +11957,7 @@
         }, 
         {
             "location": "/faq/answers/", 
-            "text": "How do I submit a bug?\n\n\n\n\nIf you do not have a JIRA account sign up for an account on \nJIRA\n.\n\n\nSubmit a request to the @dev mailing list for your JIRA username to be added to the Apache Mynewt (MYNEWT) project. You can view the issues on JIRA for the MYNEWT project without an account but you need to log in for reporting a bug. \n\n\nLog in. Choose the \"MYNEWT\" project. Click on the \"Create\" button to create a ticket. Choose \"Bug\" as the Issue Type. Fill in the bug description, how it is triggered, and other details. \n\n\nHow do I request a feature?\n\n\n\n\nIf you do not have a JIRA account sign up for an account on \nJIRA\n.\n\n\nSubmit a request to the @dev mailing list for your JIRA username to be added to the Apache Mynewt (MYNEWT) project. You can view the issues on JIRA for the MYNEWT project without an account but you need to log in for reporting a bug. \n\n\nLog in. Choose the \"MYNEWT\" project. Click on the \"Create\" button to creat
 e a ticket. Choose \"Wish\" as the Issue Type. Fill in the feature description,  benefits, and any other implementation details. Note in the description whether you want to work on it yourself. \n\n\nIf you are not a committer and you wish to work on it, someone who is on the committer list will have to review your request and assign it to you. You will have to refer to this JIRA ticket in your pull request.\n\n\nI am not on the committer list. How do I submit a patch?\n\n\n\n\nYou submit your proposed changes for your peers with committer status to review and merge.\n\n\nThe \"develop\" branch on Mynewt's repository contains the most recent changes made by the community of developers. Contributions from you need to go into this branch. The essential steps to setting up your project space for working with the latest code from \"develop\" and make pull requests into \"develop\" to get your code added are the following:\n\n\nStep 1:\n Create a fork of the entire Mynewt repository on g
 ithub.com.\n\n\nStep 2:\n Setup repository on your laptop to use code in \u201cdevelop\u201d branch. You then create a new branch \u201cmybranch\u201d using \u201cgit checkout \u2013b\u201d. You also add a remote handle named \u201cfork\u201d that points to the github fork you created in Step 1.\n\n\n    $ newt new devproject\n    $ cd devproject\n    $ vi project.yml\n        # change version to 0-dev for repository.apache-mynewt-core\n    $ newt install\n    $ cd repos/apache-mynewt-core\n    $ git status\n        On branch develop\n        Your branch is up-to-date with \norigin/develop\n.\n        nothing to commit, working directory clean\n    $ git checkout \u2013b mybranch\n    $ git remote -v\n        origin https://github.com/apache/incubator-mynewt-core.git (fetch) \n        origin https://github.com/apache/incubator-mynewt-core.git (push)\n    $ git remote add fork https://github.com/\nuser\n/incubator-mynewt-core \n    $ git remote -v\n        origin https://github.com/a
 pache/incubator-mynewt-core.git (fetch) \n        origin https://github.com/apache/incubator-mynewt-core.git (push)\n        fork https://github.com/\nuser\n/incubator-mynewt-core (fetch) \n        fork https://github.com/\nuser\n/incubator-mynewt-core (push)\n\n\n\n\n\nStep 3:\n Check you are in \u201cmybranch\u201d. Write code. Stage and commit your changes\n(example shows adding all).\n\n\n   $ git checkout mybranch\n   $ git add .\n   $ git commit \u2013m \u201cyour message about your code changes\u201d\n\n\n\n\n\nStep 4:\n Always pull the latest from develop on Apache mirror to \u201cmybranch\u201d before pushing any changes to remotes. If you see merge conflicts, resolve them first.\n\n\n   $ git pull --rebase origin develop\n\n\n\n\n\nStep 5:\n Push your changes to \u201cmybranch\u201d branch on your github fork. If \u201cmybranch\u201d does not exist yet on your github fork, the command automa;cally creates it.\n\n\n   $ git push fork mybranch\n\n\n\n\n\n\ufffcStep 6:\n Gene
 rate a pull request from \u201cmybranch\u201d in your fork to \u201cdevelop\u201d in Mynewt using the \"New pull request\" button on github.com.\n\n\n\n\nI would like to make some edits to the documentation. What do I do?\n\n\n\n\nYou submit your proposed changes for your peers with committer status to review and merge. \n\n\nGo to the \ndocumentation mirror\n on github.com.\n\n\nNavigate to the file you wish to edit on github.com. All the technical documentation is in Markdown files under the \n/docs\n directory. Click on the pencil icon (\"Edit the file in your fork of this project\") and start making changes.\n\n\nClick the green \"Propose file change\" button. You will be directed to the page where you can start a pull request from the branch that was created for you. The branch is gets an automatic name \npatch-#\n where # is a number. Click on the green \"Compare \n pull request\" to open the pull request.\n\n\nIn the comment for the pull request, include a description of the 
 changes you have made and why. Github will automatically notify everyone on the commits@mynewt.incubator.apache.org mailing list about the newly opened pull requests. You can open a pull request even if you don't think the code is ready for merging but want some discussion on the matter.\n\n\nUpon receiving notification, one or more committers will review your work, ask for edits or clarifications, and merge when your proposed changes are ready.\n\n\nIf you want to withdraw the pull request simply go to your fork \nhttps://github.com/\nyour github username\n/incubator-mynewt-site\n and click on \"branches\". You should see your branch under \"Your branches\". Click on the delete icon.\n\n\nI would like to make some edits to the documentation but want to use an editor on my own laptop. What do I do?\n\n\n\n\nYou submit your proposed changes for your peers with committer status to review and merge. \n\n\nGo to the \ndocumentation mirror\n on github.com. You need to create your own for
 k of the repo in github.com by clicking on the \"Fork\" button on the top right. Clone the forked repository into your laptop (using \ngit clone\n from a terminal or using the download buttons on the github page)and create a local branch for the edits and switching to it (using \ngit checkout -b \nnew-branchname\n or GitHub Desktop). \n\n\nMake your changes using the editor of your choice. Push that branch to your fork on github. Then submit a pull request from that branch on your github fork.\n\n\nThe review and merge process is the same as other pull requests described for earlier questions.", 
+            "text": "How do I submit a bug?\n\n\n\n\nIf you do not have a JIRA account sign up for an account on \nJIRA\n.\n\n\nSubmit a request to the @dev mailing list for your JIRA username to be added to the Apache Mynewt (MYNEWT) project. You can view the issues on JIRA for the MYNEWT project without an account but you need to log in for reporting a bug. \n\n\nLog in. Choose the \"MYNEWT\" project. Click on the \"Create\" button to create a ticket. Choose \"Bug\" as the Issue Type. Fill in the bug description, how it is triggered, and other details. \n\n\nHow do I request a feature?\n\n\n\n\nIf you do not have a JIRA account sign up for an account on \nJIRA\n.\n\n\nSubmit a request to the @dev mailing list for your JIRA username to be added to the Apache Mynewt (MYNEWT) project. You can view the issues on JIRA for the MYNEWT project without an account but you need to log in for reporting a bug. \n\n\nLog in. Choose the \"MYNEWT\" project. Click on the \"Create\" button to creat
 e a ticket. Choose \"Wish\" as the Issue Type. Fill in the feature description,  benefits, and any other implementation details. Note in the description whether you want to work on it yourself. \n\n\nIf you are not a committer and you wish to work on it, someone who is on the committer list will have to review your request and assign it to you. You will have to refer to this JIRA ticket in your pull request.\n\n\nI am not on the committer list. How do I submit a patch?\n\n\n\n\nYou submit your proposed changes for your peers with committer status to review and merge.\n\n\nThe process to submit a Pull Request on github.com is described on the \nConfluence page for the project\n. \n\n\nI am a committer in the project. Can I merge my own Pull Request into the git repository?\n\n\nYes, but only if your Pull Request has been reviewed and approved by another committer in Apache Mynewt.\nThe process to merge a Pull Request is described on the \nConfluence page for the project\n.\n\n\nI wou
 ld like to make some edits to the documentation. What do I do?\n\n\n\n\nYou submit your proposed changes for your peers with committer status to review and merge. \n\n\nGo to the \ndocumentation mirror\n on github.com.\n\n\nNavigate to the file you wish to edit on github.com. All the technical documentation is in Markdown files under the \n/docs\n directory. Click on the pencil icon (\"Edit the file in your fork of this project\") and start making changes.\n\n\nClick the green \"Propose file change\" button. You will be directed to the page where you can start a pull request from the branch that was created for you. The branch is gets an automatic name \npatch-#\n where # is a number. Click on the green \"Compare \n pull request\" to open the pull request.\n\n\nIn the comment for the pull request, include a description of the changes you have made and why. Github will automatically notify everyone on the commits@mynewt.incubator.apache.org mailing list about the newly opened pull re
 quests. You can open a pull request even if you don't think the code is ready for merging but want some discussion on the matter.\n\n\nUpon receiving notification, one or more committers will review your work, ask for edits or clarifications, and merge when your proposed changes are ready.\n\n\nIf you want to withdraw the pull request simply go to your fork \nhttps://github.com/\nyour github username\n/incubator-mynewt-site\n and click on \"branches\". You should see your branch under \"Your branches\". Click on the delete icon.\n\n\nI would like to make some edits to the documentation but want to use an editor on my own laptop. What do I do?\n\n\n\n\nYou submit your proposed changes for your peers with committer status to review and merge. \n\n\nGo to the \ndocumentation mirror\n on github.com. You need to create your own fork of the repo in github.com by clicking on the \"Fork\" button on the top right. Clone the forked repository into your laptop (using \ngit clone\n from a termi
 nal or using the download buttons on the github page)and create a local branch for the edits and switching to it (using \ngit checkout -b \nnew-branchname\n or GitHub Desktop). \n\n\nMake your changes using the editor of your choice. Push that branch to your fork on github. Then submit a pull request from that branch on your github fork.\n\n\nThe review and merge process is the same as other pull requests described for earlier questions.", 
             "title": "FAQ"
         }, 
         {
@@ -11972,10 +11972,15 @@
         }, 
         {
             "location": "/faq/answers/#i-am-not-on-the-committer-list-how-do-i-submit-a-patch", 
-            "text": "You submit your proposed changes for your peers with committer status to review and merge.  The \"develop\" branch on Mynewt's repository contains the most recent changes made by the community of developers. Contributions from you need to go into this branch. The essential steps to setting up your project space for working with the latest code from \"develop\" and make pull requests into \"develop\" to get your code added are the following:  Step 1:  Create a fork of the entire Mynewt repository on github.com.  Step 2:  Setup repository on your laptop to use code in \u201cdevelop\u201d branch. You then create a new branch \u201cmybranch\u201d using \u201cgit checkout \u2013b\u201d. You also add a remote handle named \u201cfork\u201d that points to the github fork you created in Step 1.      $ newt new devproject\n    $ cd devproject\n    $ vi project.yml\n        # change version to 0-dev for repository.apache-mynewt-core\n    $ newt install\n    $ cd repos/apac
 he-mynewt-core\n    $ git status\n        On branch develop\n        Your branch is up-to-date with  origin/develop .\n        nothing to commit, working directory clean\n    $ git checkout \u2013b mybranch\n    $ git remote -v\n        origin https://github.com/apache/incubator-mynewt-core.git (fetch) \n        origin https://github.com/apache/incubator-mynewt-core.git (push)\n    $ git remote add fork https://github.com/ user /incubator-mynewt-core \n    $ git remote -v\n        origin https://github.com/apache/incubator-mynewt-core.git (fetch) \n        origin https://github.com/apache/incubator-mynewt-core.git (push)\n        fork https://github.com/ user /incubator-mynewt-core (fetch) \n        fork https://github.com/ user /incubator-mynewt-core (push)  Step 3:  Check you are in \u201cmybranch\u201d. Write code. Stage and commit your changes\n(example shows adding all).     $ git checkout mybranch\n   $ git add .\n   $ git commit \u2013m \u201cyour message about your code chan
 ges\u201d  Step 4:  Always pull the latest from develop on Apache mirror to \u201cmybranch\u201d before pushing any changes to remotes. If you see merge conflicts, resolve them first.     $ git pull --rebase origin develop  Step 5:  Push your changes to \u201cmybranch\u201d branch on your github fork. If \u201cmybranch\u201d does not exist yet on your github fork, the command automa;cally creates it.     $ git push fork mybranch  \ufffcStep 6:  Generate a pull request from \u201cmybranch\u201d in your fork to \u201cdevelop\u201d in Mynewt using the \"New pull request\" button on github.com.", 
+            "text": "You submit your proposed changes for your peers with committer status to review and merge.  The process to submit a Pull Request on github.com is described on the  Confluence page for the project .", 
             "title": "I am not on the committer list. How do I submit a patch?"
         }, 
         {
+            "location": "/faq/answers/#i-am-a-committer-in-the-project-can-i-merge-my-own-pull-request-into-the-git-repository", 
+            "text": "Yes, but only if your Pull Request has been reviewed and approved by another committer in Apache Mynewt.\nThe process to merge a Pull Request is described on the  Confluence page for the project .", 
+            "title": "I am a committer in the project. Can I merge my own Pull Request into the git repository?"
+        }, 
+        {
             "location": "/faq/answers/#i-would-like-to-make-some-edits-to-the-documentation-what-do-i-do", 
             "text": "You submit your proposed changes for your peers with committer status to review and merge.   Go to the  documentation mirror  on github.com.  Navigate to the file you wish to edit on github.com. All the technical documentation is in Markdown files under the  /docs  directory. Click on the pencil icon (\"Edit the file in your fork of this project\") and start making changes.  Click the green \"Propose file change\" button. You will be directed to the page where you can start a pull request from the branch that was created for you. The branch is gets an automatic name  patch-#  where # is a number. Click on the green \"Compare   pull request\" to open the pull request.  In the comment for the pull request, include a description of the changes you have made and why. Github will automatically notify everyone on the commits@mynewt.incubator.apache.org mailing list about the newly opened pull requests. You can open a pull request even if you don't think the code is re
 ady for merging but want some discussion on the matter.  Upon receiving notification, one or more committers will review your work, ask for edits or clarifications, and merge when your proposed changes are ready.  If you want to withdraw the pull request simply go to your fork  https://github.com/ your github username /incubator-mynewt-site  and click on \"branches\". You should see your branch under \"Your branches\". Click on the delete icon.", 
             "title": "I would like to make some edits to the documentation. What do I do?"

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/02116bd4/develop/newt/install/newt_linux/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/install/newt_linux/index.html b/develop/newt/install/newt_linux/index.html
index 9e5bd62..beed80e 100644
--- a/develop/newt/install/newt_linux/index.html
+++ b/develop/newt/install/newt_linux/index.html
@@ -439,8 +439,8 @@ $sudo apt-get install apt-transport-https
 <div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo -s
 [sudo] password for &lt;user&gt;:
 root$ cat &gt; /etc/apt/sources.list.d/mynewt.list &lt;&lt;EOF
-deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
-deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+deb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main
+deb-src https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main
 EOF
 root$exit
 </pre></div>
@@ -450,8 +450,8 @@ root$exit
 <p><br>
 Verify the content of the source list file:</p>
 <div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$more /etc/apt/sources.list.d/mynewt.list
-deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
-deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+deb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main
+deb-src https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main
 </pre></div>
 
 

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/02116bd4/develop/newtmgr/install_linux/index.html
----------------------------------------------------------------------
diff --git a/develop/newtmgr/install_linux/index.html b/develop/newtmgr/install_linux/index.html
index d955629..1ff2c9b 100644
--- a/develop/newtmgr/install_linux/index.html
+++ b/develop/newtmgr/install_linux/index.html
@@ -417,8 +417,8 @@ $sudo apt-get install apt-transport-https
 <div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo -s
 [sudo] password for &lt;user&gt;:
 root$ cat &gt; /etc/apt/sources.list.d/mynewt.list &lt;&lt;EOF
-deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
-deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+deb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main
+deb-src https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main
 EOF
 root$exit
 </pre></div>
@@ -428,8 +428,8 @@ root$exit
 <p><br>
 Verify the content of the source list file:</p>
 <div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$more /etc/apt/sources.list.d/mynewt.list
-deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
-deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
+deb https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main
+deb-src https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest main
 </pre></div>
 
 

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/02116bd4/develop/os/get_started/native_install_intro/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/native_install_intro/index.html b/develop/os/get_started/native_install_intro/index.html
index e8df52f..816bcf4 100644
--- a/develop/os/get_started/native_install_intro/index.html
+++ b/develop/os/get_started/native_install_intro/index.html
@@ -412,7 +412,7 @@
 <ul>
 <li>
 <p>Native toolchain - Native toolchain to build and run Mynewt OS as a native application on your computer.
-  (See <a href="/os/get_started/native_install.md">Installing Native Toolchain</a>).  </p>
+  (See <a href="../native_tools/">Installing Native Toolchain</a>).  </p>
 </li>
 <li>
 <p>Cross toolchain for ARM - Cross toolchain for ARM to build and run a Mynewt OS application on a target board

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/02116bd4/develop/os/tutorials/blinky_stm32f4disc/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blinky_stm32f4disc/index.html b/develop/os/tutorials/blinky_stm32f4disc/index.html
index 3cf584b..00def05 100644
--- a/develop/os/tutorials/blinky_stm32f4disc/index.html
+++ b/develop/os/tutorials/blinky_stm32f4disc/index.html
@@ -542,7 +542,7 @@
 <li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
 <li>Have a STM32F4-Discovery board.</li>
 <li>Have a USB type A to Mini-B cable.    </li>
-<li>Install a patched version of OpenOCD 0.10.0 described in <a href="../os/get_started/cross_tools/">Install OpenOCD</a>.  </li>
+<li>Install a patched version of OpenOCD 0.10.0 described in <a href="../../../os/get_started/cross_tools/">Install OpenOCD</a>.  </li>
 </ul>
 <h3 id="create-a-project">Create a Project</h3>
 <p>Create a new project if you do not have an existing one.  You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created.  </p>

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/02116bd4/develop/os/tutorials/rbnano2/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/rbnano2/index.html b/develop/os/tutorials/rbnano2/index.html
index bbe63a4..227d285 100644
--- a/develop/os/tutorials/rbnano2/index.html
+++ b/develop/os/tutorials/rbnano2/index.html
@@ -540,7 +540,7 @@
 <ul>
 <li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
 <li>Have a RedBear Nano 2 board. </li>
-<li>Install a patched version of OpenOCD 0.10.0 described in <a href="../os/get_started/cross_tools/">Install OpenOCD</a>.</li>
+<li>Install a patched version of OpenOCD 0.10.0 described in <a href="../../../os/get_started/cross_tools/">Install OpenOCD</a>.</li>
 </ul>
 <h3 id="create-a-project">Create a Project</h3>
 <p>Create a new project if you do not have an existing one.  You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created.  </p>

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/02116bd4/develop/sitemap.xml
----------------------------------------------------------------------
diff --git a/develop/sitemap.xml b/develop/sitemap.xml
index bdc2916..575d20f 100644
--- a/develop/sitemap.xml
+++ b/develop/sitemap.xml
@@ -4,7 +4,7 @@
     
     <url>
      <loc>http://mynewt.apache.org/</loc>
-     <lastmod>2017-05-05</lastmod>
+     <lastmod>2017-05-08</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -13,7 +13,7 @@
         
     <url>
      <loc>http://mynewt.apache.org/pages/ble/</loc>
-     <lastmod>2017-05-05</lastmod>
+     <lastmod>2017-05-08</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
@@ -22,7 +22,7 @@
     
     <url>
      <loc>http://mynewt.apache.org/quick-start/</loc>
-     <lastmod>2017-05-05</lastmod>
+     <lastmod>2017-05-08</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -30,7 +30,7 @@
     
     <url>
      <loc>http://mynewt.apache.org/about/</loc>
-     <lastmod>2017-05-05</lastmod>
+     <lastmod>2017-05-08</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -38,7 +38,7 @@
     
     <url>
      <loc>http://mynewt.apache.org/talks/</loc>
-     <lastmod>2017-05-05</lastmod>
+     <lastmod>2017-05-08</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -46,7 +46,7 @@
     
     <url>
      <loc>http://mynewt.apache.org/download/</loc>
-     <lastmod>2017-05-05</lastmod>
+     <lastmod>2017-05-08</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -54,7 +54,7 @@
     
     <url>
      <loc>http://mynewt.apache.org/community/</loc>
-     <lastmod>2017-05-05</lastmod>
+     <lastmod>2017-05-08</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -62,7 +62,7 @@
     
     <url>
      <loc>http://mynewt.apache.org/events/</loc>
-     <lastmod>2017-05-05</lastmod>
+     <lastmod>2017-05-08</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -71,7 +71,7 @@
         
     <url>
      <loc>http://mynewt.apache.org/os/introduction/</loc>
-     <lastmod>2017-05-05</lastmod>
+     <lastmod>2017-05-08</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
@@ -83,7 +83,7 @@
         
     <url>
      <loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
-     <lastmod>2017-05-05</lastmod>
+     <lastmod>2017-05-08</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
@@ -123,19 +123,19 @@
         
     <url>
      <loc>http://mynewt.apache.org/faq/go_env/</loc>
-     <lastmod>2017-05-05</lastmod>
+     <lastmod>2017-05-08</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
-     <lastmod>2017-05-05</lastmod>
+     <lastmod>2017-05-08</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://mynewt.apache.org/faq/answers/</loc>
-     <lastmod>2017-05-05</lastmod>
+     <lastmod>2017-05-08</lastmod>
      <changefreq>daily</changefreq>
     </url>
         

http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/02116bd4/latest/faq/answers/index.html
----------------------------------------------------------------------
diff --git a/latest/faq/answers/index.html b/latest/faq/answers/index.html
index 9cb9e41..a7dff75 100644
--- a/latest/faq/answers/index.html
+++ b/latest/faq/answers/index.html
@@ -276,52 +276,10 @@
 <h3 id="i-am-not-on-the-committer-list-how-do-i-submit-a-patch">I am not on the committer list. How do I submit a patch?</h3>
 <p><br></p>
 <p><strong>You submit your proposed changes for your peers with committer status to review and merge.</strong></p>
-<p>The "develop" branch on Mynewt's repository contains the most recent changes made by the community of developers. Contributions from you need to go into this branch. The essential steps to setting up your project space for working with the latest code from "develop" and make pull requests into "develop" to get your code added are the following:</p>
-<p><strong>Step 1:</strong> Create a fork of the entire Mynewt repository on github.com.</p>
-<p><strong>Step 2:</strong> Setup repository on your laptop to use code in “develop” branch. You then create a new branch “mybranch” using “git checkout –b”. You also add a remote handle named “fork” that points to the github fork you created in Step 1.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">    $ newt new devproject
-    $ cd devproject
-    $ vi project.yml
-        # change version to 0-dev for repository.apache-mynewt-core
-    $ newt install
-    $ cd repos/apache-mynewt-core
-    $ git status
-        On branch develop
-        Your branch is up-to-date with &#39;origin/develop&#39;.
-        nothing to commit, working directory clean
-    $ git checkout –b mybranch
-    $ git remote -v
-        origin https://github.com/apache/incubator-mynewt-core.git (fetch) 
-        origin https://github.com/apache/incubator-mynewt-core.git (push)
-    $ git remote add fork https://github.com/&lt;user&gt;/incubator-mynewt-core 
-    $ git remote -v
-        origin https://github.com/apache/incubator-mynewt-core.git (fetch) 
-        origin https://github.com/apache/incubator-mynewt-core.git (push)
-        fork https://github.com/&lt;user&gt;/incubator-mynewt-core (fetch) 
-        fork https://github.com/&lt;user&gt;/incubator-mynewt-core (push)
-</pre></div>
-
-
-<p><strong>Step 3:</strong> Check you are in “mybranch”. Write code. Stage and commit your changes
-(example shows adding all).</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">   $ git checkout mybranch
-   $ git add .
-   $ git commit –m “your message about your code changes”
-</pre></div>
-
-
-<p><strong>Step 4:</strong> Always pull the latest from develop on Apache mirror to “mybranch” before pushing any changes to remotes. If you see merge conflicts, resolve them first.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">   $ git pull --rebase origin develop
-</pre></div>
-
-
-<p><strong>Step 5:</strong> Push your changes to “mybranch” branch on your github fork. If “mybranch” does not exist yet on your github fork, the command automa;cally creates it.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">   $ git push fork mybranch
-</pre></div>
-
-
-<p><strong>Step 6:</strong> Generate a pull request from “mybranch” in your fork to “develop” in Mynewt using the "New pull request" button on github.com.</p>
-<p><img alt="Mynewt Dev Cycle" src="../mynewt_dev_cycle.jpg" /></p>
+<p>The process to submit a Pull Request on github.com is described on the <a href="https://cwiki.apache.org/confluence/display/MYNEWT/Submitting+Pull+Requests">Confluence page for the project</a>. </p>
+<h3 id="i-am-a-committer-in-the-project-can-i-merge-my-own-pull-request-into-the-git-repository">I am a committer in the project. Can I merge my own Pull Request into the git repository?</h3>
+<p>Yes, but only if your Pull Request has been reviewed and approved by another committer in Apache Mynewt.
+The process to merge a Pull Request is described on the <a href="https://cwiki.apache.org/confluence/display/MYNEWT/Merging+Pull+Requests">Confluence page for the project</a>.</p>
 <h3 id="i-would-like-to-make-some-edits-to-the-documentation-what-do-i-do">I would like to make some edits to the documentation. What do I do?</h3>
 <p><br></p>
 <p>You submit your proposed changes for your peers with committer status to review and merge. </p>


Mime
View raw message