Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Chase Maupin <chase.maupin@ti.com>, Koen Kooi <k-kooi@ti.com>
Subject: Re: [PATCH 1/7] Usermanual/common_use_cases: Fix documentation errors
Date: Wed, 26 May 2010 09:38:22 +0200	[thread overview]
Message-ID: <20100526073822.GA31532@mx.loc> (raw)
In-Reply-To: <1274854676-5931-1-git-send-email-koen@openembedded.org>

On Wed, May 26, 2010 at 08:17:50AM +0200, Koen Kooi wrote:
>From: Chase Maupin <chase.maupin@ti.com>
>
>* Fixed up typos and other errors in the documentation.
>
>Signed-off-by: Chase Maupin <chase.maupin@ti.com>
>Signed-off-by: Koen Kooi <k-kooi@ti.com>
>---
> docs/usermanual/chapters/common_use_cases.xml |   45 +++++++++++++-----------
> 1 files changed, 24 insertions(+), 21 deletions(-)
>
>diff --git a/docs/usermanual/chapters/common_use_cases.xml b/docs/usermanual/chapters/common_use_cases.xml
>index 7ae3ee5..9adb66a 100644
>--- a/docs/usermanual/chapters/common_use_cases.xml
>+++ b/docs/usermanual/chapters/common_use_cases.xml

>@@ -575,7 +578,7 @@ $ <command>bitbake</command> meta-toolchain-qte
>             should start by downloading the SDK and untar it to the root folder
>             (<filename>/</filename>). Once this operation is finished you will
>             find a new directory <filename>/usr/local/angstrom/arm/</filename> and
>-            it contains the <filename>environment-setup</filename> to setup the
>+            it contains the <filename>environment-setup</filename>file to setup the

missing space before "file" ?

>             <emphasis>QMAKESPEC</emphasis> and various other paths.
>             </para>



      parent reply	other threads:[~2010-05-26  7:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26  6:17 [PATCH 1/7] Usermanual/common_use_cases: Fix documentation errors Koen Kooi
2010-05-26  6:17 ` [PATCH 2/7] Usermanual/comparing: " Koen Kooi
2010-05-26  6:48   ` Stefan Schmidt
2010-05-26  6:17 ` [PATCH 3/7] Usermanual/features: " Koen Kooi
2010-05-26  6:49   ` Stefan Schmidt
2010-05-26  7:40   ` Bernhard Reutner-Fischer
2010-05-26  6:17 ` [PATCH 4/7] Usermanual/getting_oe: " Koen Kooi
2010-05-26  6:49   ` Stefan Schmidt
2010-05-26  7:42   ` Bernhard Reutner-Fischer
2010-05-26  6:17 ` [PATCH 5/7] Usermanual/metadata: " Koen Kooi
2010-05-26  6:49   ` Stefan Schmidt
2010-05-26  8:06   ` Bernhard Reutner-Fischer
2010-05-26  6:17 ` [PATCH 6/7] Usermanual/recipes: " Koen Kooi
2010-05-26  6:49   ` Stefan Schmidt
2010-05-26  6:17 ` [PATCH 7/7] Usermanual/usage: " Koen Kooi
2010-05-26  6:49   ` Stefan Schmidt
2010-05-26  6:48 ` [PATCH 1/7] Usermanual/common_use_cases: " Stefan Schmidt
2010-05-26  7:38 ` Bernhard Reutner-Fischer [this message]

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=20100526073822.GA31532@mx.loc \
    --to=rep.dot.nop@gmail.com \
    --cc=chase.maupin@ti.com \
    --cc=k-kooi@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