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 3/7] features: Fix documentation errors
Date: Wed, 26 May 2010 12:30:05 -0400	[thread overview]
Message-ID: <20100526163005.GF23464@denix.org> (raw)
In-Reply-To: <1274879375-19626-3-git-send-email-chase.maupin@ti.com>

On Wed, May 26, 2010 at 08:09:31AM -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/features.xml |   10 +++++-----
>  1 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/docs/usermanual/chapters/features.xml b/docs/usermanual/chapters/features.xml
> index 3cbf1d8..880b75c 100644
> --- a/docs/usermanual/chapters/features.xml
> +++ b/docs/usermanual/chapters/features.xml
> @@ -22,9 +22,9 @@
>      <para>Run-time Dependencies (<command>RDEPENDS</command>) will be added
>      when packaging the software. They should only contain the minimal
>      dependencies to run the program. OpenEmbedded will analyze each packaged
> -    binary and search for <command>SO_NEEDED</command> libraries. The
> -    libraries are absolutely required by the program then OpenEmbedded is
> -    searching for packages that installs these libraries. these packages are
> +    binary and search for <command>SO_NEEDED</command> libraries. These
> +    libraries are absolutely required by the program so OpenEmbedded will
> +    search for packages that install these libraries. These packages are
>      automatically added to the <command>RDEPENDS</command>. As a packager you
>      don't need to worry about shared libraries anymore they will be added
>      automatically.</para>
> @@ -52,9 +52,9 @@ BBFILE_PRIORITY_local = "10"
>      <title>Task-base <anchor id="task-base" /></title>
>  
>      <para>Task-base is new way of creating basic root filesystems. Instead of
> -    having each machine setting a ton of duplicate variables, this allow a
> +    having each machine setting a ton of duplicate variables, this allows a
>      machine to specify its features and <command>task-base</command> builds it
> -    a customised package based on what the machine needs along with what the
> +    a customized package based on what the machine needs along with what the
>      distro supports.</para>
>  
>      <para>To illustrate, the distro config file can say: <screen>
> -- 
> 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       ` [PATCHv2 4/7] getting_oe: " Denys Dmytriyenko
2010-05-26 16:30     ` Denys Dmytriyenko [this message]
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=20100526163005.GF23464@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