GitHub user ccollins476ad opened a pull request:

    https://github.com/apache/incubator-mynewt-site/pull/145

    mfg docs - slight rewording / rearranging

    1. Move create mfg step such that it comes before the boot-build and
    create-image steps.
    
    Rationale: The mfg package only needs to be created once, whereas the
    boot loader and image need to be rebuilt each time a new mfg image is
    built.  It makes sense to group the steps that need to be repeated
    together.
    
    2. Remove redundant 'newt build rb_boot' line from example
    
    This line was accidentally duplicated.
    
    3. Slight rewording of some text to keep vocabulary consistent (mfg
    package versus manufacturing image).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ccollins476ad/incubator-mynewt-site mfg-fix

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-mynewt-site/pull/145.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 #145
    
----
commit d682564a9e5ea6e92db25ab989030b7880e43add
Author: Christopher Collins <[email protected]>
Date:   2017-01-23T17:15:59Z

    mfg docs - slight rewording / rearranging
    
    1. Move create mfg step such that it comes before the boot-build and
    create-image steps.
    
    Rationale: The mfg package only needs to be created once, whereas the
    boot loader and image need to be rebuilt each time a new mfg image is
    built.  It makes sense to group the steps that need to be repeated
    together.
    
    2. Remove redundant 'newt build rb_boot' line from example
    
    This line was accidentally duplicated.
    
    3. Slight rewording of some text to keep vocabulary consistent (mfg
    package versus manufacturing image).

----


---
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.
---

Reply via email to