Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: Chase Maupin <chase.maupin@ti.com>
Subject: Re: [PATCHv2 4/7] getting_oe: Fix documentation errors
Date: Wed, 26 May 2010 12:30:16 -0400	[thread overview]
Message-ID: <20100526163016.GG23464@denix.org> (raw)
In-Reply-To: <1274879375-19626-4-git-send-email-chase.maupin@ti.com>

On Wed, May 26, 2010 at 08:09:32AM -0500, Chase Maupin wrote:
> * Fixed up typos and other errors in the documentation.
> 
> Signed-off-by: Chase Maupin <chase.maupin@ti.com>

Acked-by: Denys Dmytriyenko <denis@denix.org>

> ---
>  docs/usermanual/chapters/getting_oe.xml |   26 ++++++++++++++++++++++----
>  1 files changed, 22 insertions(+), 4 deletions(-)
> 
> diff --git a/docs/usermanual/chapters/getting_oe.xml b/docs/usermanual/chapters/getting_oe.xml
> index d18c955..c82df3a 100644
> --- a/docs/usermanual/chapters/getting_oe.xml
> +++ b/docs/usermanual/chapters/getting_oe.xml
> @@ -98,7 +98,7 @@ $ <command>git</command> clone git://git.openembedded.org/openembedded</screen>
>          seems good practice to update your OpenEmbedded tree at least
>          daily. To do this, run:
>          <screen>
> -$ <command>cd</command> $OEBASE
> +$ <command>cd</command> $OEBASE/openembedded
>  $ <command>git</command> pull</screen>
>        </para>
>      </section>
> @@ -142,7 +142,7 @@ $ <command>git</command> pull</screen>
>  
>        <para>Since the path to your OpenEmbedded installation will be used in
>          many places, setting it in your environment will allow you to use
> -        the <varname>$OEBASE</varname> variable in all pathes and make it
> +        the <varname>$OEBASE</varname> variable in all paths and make it
>          easier to change in the future should the need arise. To
>          set <varname>$OEBASE</varname> if you use a Bourne like shell
>          <footnote>
> @@ -342,6 +342,16 @@ MACHINE = "om-gta01"</screen>
>              </varlistentry>
>  
>              <varlistentry>
> +              <term><literal>base-image</literal></term>
> +              <listitem>
> +                <para>Build an image that is the smallest possible image
> +                  which allows for ssh access and the ability to install
> +                  additional packages using ipkg.
> +                </para>
> +              </listitem>
> +            </varlistentry>
> +
> +            <varlistentry>
>                <term><literal>console-image</literal></term>
>                <listitem>
>                  <para>Build an image without the X11, gtk+, or qt windowing
> @@ -463,9 +473,10 @@ MACHINE = "om-gta01"</screen>
>              </varlistentry>
>  
>              <varlistentry>
> -              <term><literal>task-native-sdk</literal></term>
> +              <term><literal>task-sdk-native</literal></term>
>                <listitem>
> -                <para>Mata-package for native (on-device) SDK.
> +                <para>Meta-package for native (on-device) SDK.  i.e. libc, gcc,
> +                  make, etc.
>                  </para>
>                </listitem>
>              </varlistentry>
> @@ -536,6 +547,13 @@ MACHINE = "om-gta01"</screen>
>                  <para>Builds the appropriate kernel for your device.</para>
>                </listitem>
>              </varlistentry>
> +
> +            <varlistentry>
> +              <term><literal>virtual/bootloader</literal></term>
> +              <listitem>
> +                <para>Builds the appropriate bootloader for your device.</para>
> +              </listitem>
> +            </varlistentry>
>            </variablelist>
>          </para>
>        </section>
> -- 
> 1.6.0.4
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  parent reply	other threads:[~2010-05-26 16:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 13:09 [PATCHv2 1/7] common_use_cases: Fix documentation errors Chase Maupin
2010-05-26 13:09 ` [PATCHv2 2/7] comparing: " Chase Maupin
2010-05-26 13:09   ` [PATCHv2 3/7] features: " Chase Maupin
2010-05-26 13:09     ` [PATCHv2 4/7] getting_oe: " Chase Maupin
2010-05-26 13:09       ` [PATCHv2 5/7] metadata: " Chase Maupin
2010-05-26 13:09         ` [PATCHv2 6/7] recipes: " Chase Maupin
2010-05-26 13:09           ` [PATCHv2 7/7] usage: " Chase Maupin
2010-05-26 16:30             ` Denys Dmytriyenko
2010-05-26 16:30           ` [PATCHv2 6/7] recipes: " Denys Dmytriyenko
2010-05-26 16:30         ` [PATCHv2 5/7] metadata: " Denys Dmytriyenko
2010-05-26 16:30       ` Denys Dmytriyenko [this message]
2010-05-26 16:30     ` [PATCHv2 3/7] features: " Denys Dmytriyenko
2010-05-26 16:29   ` [PATCHv2 2/7] comparing: " Denys Dmytriyenko
2010-05-26 16:29 ` [PATCHv2 1/7] common_use_cases: " Denys Dmytriyenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100526163016.GG23464@denix.org \
    --to=denis@denix.org \
    --cc=chase.maupin@ti.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox